This record as markdown: /tools/inggerman-mcps/agent-cancel.md
What agent_cancel does on MCP Framework Personal
AI agents invoke agent_cancel to trigger actions in MCP Framework Personal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why agent_cancel is rated High
Cancelling a job is an action that triggers an external operation (stopping/terminating a running job). It is not purely a read, and while it could be considered partially destructive, job cancellation is typically a recoverable state change rather than irreversible deletion. It falls best under Execute as it triggers an operational side effect on a running process.
From the tool's definition Cancela un job por ID (Cancels a job by ID)
Attacks that exploit this kind of access
The rule that runs agent_cancel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_cancel, this is the rule to start with:
agent_cancel stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every agent_cancel call is checked against it from then on.
Questions about agent_cancel
Cancela un job por ID. It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for agent_cancel: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP Framework Personal. Nothing to install.
agent_cancel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the agent_cancel rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for agent_cancel. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
agent_cancel is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
Across the catalogue