Your agent has a job description.

agent-assurance.yaml

1apiVersion: agent-assurance/v1
2agent: { name: analytics-helper }
3tools:
4  - name: postgres.query   type: read
5  - name: web.fetch        type: read
6autonomy: 2   # a human approves actions

Then someone adds a tool.

.mcp.json

10 "fetch": {

11 "command": "uvx",

12 "args": ["mcp-server-fetch"]

13 },

  "github": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-github"],
    "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "…" }
  }

github-actionsBotcommented just now

🤖 Agent Assurance — what this change does

❌ PROMISE BROKEN BY THIS CHANGE

Blast radius: LOW → HIGH ⬆

Promise (AA-002): PASS → FAIL

❌ Newly broken

• github.write grants write, not declared (.mcp.json:17)

• access to credential data (github), not declared (.mcp.json:17)

File and line. No LLM in the verdict.

While the agent edits.

In the pull request.

On every release — signed.

CLAUDE CODE · CURSOR · GEMINI CLI · VS CODE

agent-assurance

Declare what your agent may do. Verify it on every change.

pipx install agent-assurance