Request cancellation of a calculation task (simplified).
AI agents call cancel_calculation to permanently remove resources in Abacus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a running calculation is an irreversible action — the computation state and any intermediate results are lost. This cannot be undone once the task is terminated, making it Destructive in nature. Severity is high because cancelling a long-running quantum chemistry or materials science calculation (potentially hours/days of compute) results in permanent loss of progress and wasted resources.
From the tool's definition cancel_calculation - 'Request cancellation of a calculation task'
Documented attack patterns abuse exactly the kind of access cancel_calculation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Abacus, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_calculation:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_calculation"
]
} cancel_calculation 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.
Request cancellation of a calculation task (simplified). It is categorised as a Destructive tool in the Abacus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Abacus MCP server in PolicyLayer and add a rule for cancel_calculation: 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 Abacus. Nothing to install.
cancel_calculation 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_calculation 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_calculation. 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_calculation is provided by the Abacus MCP server (phelanshao/abacus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Abacus, 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.
22 Abacus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.