Which of your agent’s tools need a person’s OK?
Paste the tools your agent can call. The checker sorts each one by what it does, says which should wait for a person, and writes the Claude Code setting or the code that makes them wait. No sign-up, and nothing leaves this page.
1Paste your agent's tools
Everything runs in this page. Nothing you paste is sent anywhere. A copied link holds your tools after its #, which browsers never send to a server; anyone you give it to can read them.
2What each tool should do
7 tools: 5 should wait for a person, 2 can run without asking.
- list_ordersOnly looks
"list" in the name only looks.
Runs without asking
- get_customerOnly looks
"get" in the name only looks.
Runs without asking
- update_shipping_addressChanges data
"update" in the name changes data.
Waits for a person as
mcp.shop.update_shipping_address - send_customer_emailReaches people
"send" in the name reaches people outside.
Waits for a person as
mcp.shop.send_customer_email - refund_orderMoves money
"refund" in the name moves money.
Waits for a person as
mcp.shop.refund_order - delete_customerHard to undo
"delete" in the name is hard to undo or runs code. The server marks it destructive.
Waits for a person as
mcp.shop.delete_customer - statsNot sure
Neither the name nor the description says what it does.
Waits for a person as
mcp.shop.stats
Add this to ~/.claude/settings.json. Claude Code then asks before every tool of that server except the ones that only look, including any tool the server adds later. Install the variantgate command and set its key first, as the Claude Code guide shows.
{
"hooks": {
"PreToolUse": [
{
"matcher": "mcp__shop__(?!(list_orders|get_customer)$).*",
"hooks": [
{ "type": "command", "command": "variantgate hook claude-code", "timeout": 180 }
]
}
]
}
}The hook does not know a call’s amount, so a limit rule never lets a payment through it: every one waits for a person. To let small amounts through, gate the tool in your own code instead.
How it sorts tools
Tool names usually start with a verb (refund_order) or end with one (issues.delete), so the checker reads that verb first. Where the name has none, it reads the first sentence of the description. When two signs disagree, the more cautious one wins, the same way VariantGate’s rules settle a conflict.
- Only looks
A verb that only looks, such as get, list, search, read or fetch.
list_orders, get_customer, search_docs
Let it run. It only looks.
- Changes data
A verb such as create, update, write, move or merge.
create_issue, update_record, upload_file
Ask a person. Once it is routine, a standing rule can answer.
- Not sure
Neither the name nor the first sentence of the description has a verb it knows.
stats, weather, customer
Ask a person until you have checked what it does.
- Reaches people
Send, email, post, publish, invite or share: anything that reaches a person or a public place.
send_email, post_message, publish_page
Ask a person: once it reaches someone, it cannot be unsent.
- Moves money
Pay, refund, charge, transfer or buy, or a change to an order, invoice, payment or subscription.
refund_order, create_payout, send_invoice
Send the amount. A rule lets small amounts through; above the limit a person decides.
- Hard to undo
Delete, drop, revoke, deploy, run or execute; a description that says permanently or cannot be undone; or the server's destructiveHint.
delete_customer, deploy, run_command, drop_table
Ask a person every time. Consider two people, or deny it if the agent never needs it.
What a name can’t tell you
A harmless name can hide a side effect
get_or_create_useris read as a change, butget_reportthat also emails the report is not. Check every tool the checker lets run before you trust it.Hints come from the server
MCP’s
readOnlyHintanddestructiveHintare written by the server’s author, and the MCP specification tells clients to treat them as untrusted. Here a hint can make a tool more cautious, never less.Arguments change the risk
A refund of 5 EUR and one of 5,000 EUR are the same tool. Send the amount with the request so a spending limit can tell them apart, and a person decides the big ones.
Make the risky ones ask for real
Free for one person and 100 requests a month, with no card. Make an agent key, paste the setting, and the next risky call waits for your yes in email, Slack, Teams, Discord or a phone notification.
Questions
Do you see the tools I paste?
No. The checker runs in your browser and sends nothing anywhere: not the tools you paste, not the names, not the result. You can check it in your browser's network tab.
Can I send the result to a colleague?
Press "Copy a link to this". The link holds your tools, the server name and any tiers you changed, after the # sign, which browsers never send to a server, so it still reaches nobody but the person you give it to. Changes that make a tool less careful are left out of the link on purpose: whoever opens it sees the checker's own verdict for those tools.
Which formats can I paste?
An MCP tools/list answer (with or without the JSON-RPC wrapper), OpenAI function tools from Chat Completions or the Responses API, Anthropic tool definitions, Gemini function declarations, or a plain list with one tool name per line and an optional description after a colon.
Is this a security review of my tools?
No. It reads names, descriptions and the hints an MCP server gives, so it is a fast first pass, not a review. A tool called get_report can still send email. Read each tool it says only looks before you let it run without asking, and correct any tier with the menu beside it.
Why doesn't it trust readOnlyHint?
MCP tool annotations such as readOnlyHint and destructiveHint are written by whoever wrote the server, and the MCP specification says to treat them as untrusted. The checker lets a hint make a tool more cautious, and lets readOnlyHint settle only a tool whose name says nothing. A hint never overrules a name that says the tool changes something.
What happens with a tool it cannot place?
Ask by default. A tool it cannot read is treated as one that changes things until you check it, and a tool whose name starts with get or list but mentions another verb, such as get_deploy_status, asks too until you mark it as only looking. In the generated setting and code every tool not on the look-only list waits for a person, so a tool added later asks first too.
Do I need a paid plan for the result?
The Claude Code setting works on the Free plan: every matched call waits for a person, who answers from email, Slack, Teams, Discord or a phone. Standing rules, such as letting refunds up to 50 EUR through, come with Pro.