Check a coding agent's guard settings
check_agent_setupCheck whether a coding agent's own guard settings hold, against runs the Durability Curve measured with its paid kits: Claude Code permission rules (which of 30 spellings of deleting a remote branch, force-pushing or pushing to main they let through), sandbox and bypass settings, prompt-injection exposure (WebFetch, shell network access), hook wiring and exit codes, and skill frontmatter; Cursor CLI cli.json rules; Codex config.toml sandbox mode. Send the files' text, with every env block, token, header and key removed. Returns findings, most severe first, each with what it is based on, the measured run (tool, version, date, setup, result) and the kit that tests it on this machine. Free: the counts, the first finding in full and the titles of the rest. Paid: every finding with its fix and the configuration that held. The guard check reads only the text it is sent and runs nothing. Each finding says whether it was predicted from the user's rules, read from their config or taken from the docs, and names the measured run behind it. It is not a security audit, and no finding does not mean a guard holds: only running the kit on the machine shows that.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"files": "<files>"
},
"name": "check_agent_setup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | The agent configuration files to check, up to 12, under 60,000 characters in all. | |
| versions | No | The tool versions, from claude --version, cursor-agent --version or codex --version, so findings can say whether the measured version matches yours. |