MCP Tool Approval Criteria Generator

Draft acceptance criteria for MCP clients that need an approval dialog, narrow auto-approve mode, first-call preview, and non-sensitive launch evidence before tools run.

Build criteria Read checklist Buy digital pack

Component or issue name Default mode Auto-approve scope Optional context Keep this high-level. Do not paste secrets, real customer records, private identifiers, payment details, or private screenshots.

Risk classes to include

Reads private workspace or customer context Writes, updates, deletes, or sends records Executes code, shell, browser, or deployment actions Creates or changes credentials, permissions, wallets, or auth grants Sends public or customer-visible output

Copyable criteria

Use this in an issue, PR, launch note, or internal acceptance checklist.

What the generator optimizes for

Preview

Tool name, server, arguments, destination, side-effect class, and untrusted-context involvement are visible before first use.

Consent

Auto-approval is narrow and revocable. Broad YOLO mode stays off for writes, credentials, identity, financial, and external-send actions.

Evidence

Launch evidence is non-sensitive: policy id, approval state, redaction result, denied tools, replay fixture, and rollback expectation.

This public page runs fully in the browser and does not submit, save, track, store, or send data. It is a planning aid, not legal advice, compliance certification, penetration testing, incident response, or a security guarantee.