AI agents call cancel_scan_job to permanently remove resources in SAST MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a scan job permanently terminates its execution. Unlike a pause or suspend, cancellation is irreversible — any progress made by the scan is lost and the job cannot be resumed. This maps to Destructive. Severity is medium because the blast radius is limited to losing scan results (no data deletion or financial impact), but it could disrupt security workflows or cause missed vulnerability findings.
From the tool's definition 'Cancel a running or pending scan job' — cancelling a job is an irreversible termination of an in-progress operation; the scan's partial results and execution state cannot be restored.
Documented attack patterns abuse exactly the kind of access cancel_scan_job gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAST MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_scan_job:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_scan_job"
]
}cancel_scan_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 or pending scan job. It is categorised as a Destructive tool in the SAST MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SAST MCP Server MCP server in PolicyLayer and add a rule for cancel_scan_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 SAST MCP Server. Nothing to install.
cancel_scan_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_scan_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_scan_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_scan_job is provided by the SAST MCP Server MCP server (sengtocxoen/sast-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAST 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.
39 SAST MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.