Cancel a report that is IN_QUEUE and has not yet started processing. Reports that are IN_PROGRESS or DONE cannot be cancelled.
AI agents call cancel_report to permanently remove resources in Mcp Ap2 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a queued report is effectively irreversible: the report request is destroyed and cannot be restored to IN_QUEUE status. While it does not delete financial data or move money, the action cannot be undone, placing it in the Destructive category. Severity is medium because the blast radius is limited to loss of a pending report rather than data or financial harm.
From the tool's definition 'Cancel a report that is IN_QUEUE and has not yet started processing' — cancellation of a queued report is an irreversible action (once cancelled, the report request is terminated and cannot be un-cancelled)
Documented attack patterns abuse exactly the kind of access cancel_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_report:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_report"
]
} cancel_report disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel a report that is IN_QUEUE and has not yet started processing. Reports that are IN_PROGRESS or DONE cannot be cancelled. It is categorised as a Destructive tool in the Mcp Ap2 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for cancel_report: 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 Ap2. Nothing to install.
cancel_report is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_report 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 cancel_report. 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.
cancel_report is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.