AI agents call cancel_job to permanently remove resources in SAS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a running job is an irreversible action: any computation, partial results, or state accumulated by the job up to that point is discarded and cannot be recovered. This maps to Destructive rather than Write because the operation cannot be undone. Severity is medium since the blast radius is limited to a single job, but misuse could abort critical SAS workloads or pipelines.
From the tool's definition 'Cancel a running job' — terminating an active job is irreversible; the job's in-progress work is lost and cannot be resumed.
Documented attack patterns abuse exactly the kind of access cancel_job gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_job:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_job"
]
}cancel_job 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 job. It is categorised as a Destructive tool in the SAS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SAS MCP Server MCP server in PolicyLayer and add a rule for cancel_job: 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 SAS MCP Server. Nothing to install.
cancel_job 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_job 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_job. 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_job is provided by the SAS MCP Server MCP server (sassoftware/sas-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAS MCP Server, 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.
27 SAS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.