Use cases

Where mayrun earns its keep

Concrete agent mishaps and team workflows — each mapped to packs and a fail-closed path.

• Stop destructive agent shell

  Deny rm -rf, mkfs, curl|sh, force-push, and sudo before the agent finishes the sentence.

  Developers after a near-miss

  dangerous-defaults

• Human gate for push and publish

  Require a human --approve before git push, cargo publish, or npm publish.

  Solo builders and small teams

  git-safe

• Secret and credential hygiene

  Deny ssh/aws/gnupg exfil paths; require approval to read project .env files.

  Security-minded engineers

  secrets-safe

• Plan-mode / read-only agents

  Inspection-only allowlist for agents that should look, not mutate.

  Agent builders shipping plan mode

  read-only

• Ops mutations need a human

  terraform apply, kubectl apply, and docker push require approval before they run.

  Platform / ops adjacent developers

  ops-approve

• Gate high-risk MCP upstreams

  Put mcp-proxy in front of filesystem or shell MCPs and evaluate tools/call.

  Teams wiring third-party MCP servers

  mcp-safe

• CI evidence on pull requests

  Free advisory policy compile; Pro fails the PR when receipt evidence is missing.

  Small teams that want proof agents stayed inside policy