Cancel the latest or selected Axint run by killing active child process groups. Use this when xcodebuild or a UI-test runner survived an MCP timeout or transport close. Use: use only to stop an active Axint run or stuck child process group. Effects: destructive: kills active Axint child process g...
Risk signalsAccepts file system path (cwd)
Part of the Axint server.
Free to start. No card required.
AI agents may call axint.run.cancel to permanently remove or destroy resources in Axint. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call axint.run.cancel in a loop, permanently destroying resources in Axint. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"axint.run.cancel"
]
}See the full Axint policy for all 35 tools.
These attack patterns abuse exactly the kind of access axint.run.cancel gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Cancel the latest or selected Axint run by killing active child process groups. Use this when xcodebuild or a UI-test runner survived an MCP timeout or transport close. Use: use only to stop an active Axint run or stuck child process group. Effects: destructive: kills active Axint child process groups; no network.. It is categorised as a Destructive tool in the Axint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Axint MCP server in PolicyLayer and add a rule for axint.run.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 Axint. Nothing to install.
axint.run.cancel 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 axint.run.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 axint.run.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.
axint.run.cancel is provided by the Axint MCP server (@axintai/compiler). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 35 Axint tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.