AI agents call cancel_gravity_task to permanently remove resources in Macrocosmos MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a running task is an irreversible action — once cancelled, the task's progress and any intermediate results are lost and cannot be recovered. This aligns with the Destructive category as the operation cannot be undone. Severity is medium since the blast radius is limited to losing a single task's work rather than deleting stored data.
From the tool's definition Cancel a running Gravity task
Documented attack patterns abuse exactly the kind of access cancel_gravity_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Macrocosmos MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_gravity_task:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_gravity_task"
]
}cancel_gravity_task 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 running Gravity task. It is categorised as a Destructive tool in the Macrocosmos MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Macrocosmos MCP server in PolicyLayer and add a rule for cancel_gravity_task: 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 Macrocosmos MCP. Nothing to install.
cancel_gravity_task 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_gravity_task 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_gravity_task. 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_gravity_task is provided by the Macrocosmos MCP server (macrocosm-os/macrocosmos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Macrocosmos MCP, 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.
6 Macrocosmos MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.