Clean up old completed/failed/cancelled jobs from the server.
AI agents call cleanup_scan_jobs 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.
Cleaning up jobs means permanently deleting records of completed, failed, or cancelled scan jobs from the server. This is an irreversible deletion operation; once purged, the job history and associated scan results cannot be recovered. The blast radius is medium since it affects audit trails and historical scan data rather than production application data.
From the tool's definition 'Clean up old completed/failed/cancelled jobs from the server' — removes/purges job records irreversibly
Documented attack patterns abuse exactly the kind of access cleanup_scan_jobs 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 cleanup_scan_jobs:
{
"version": "1",
"default": "deny",
"hide": [
"cleanup_scan_jobs"
]
}cleanup_scan_jobs 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.
Clean up old completed/failed/cancelled jobs from the server. 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 cleanup_scan_jobs: 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.
cleanup_scan_jobs 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 cleanup_scan_jobs 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 cleanup_scan_jobs. 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.
cleanup_scan_jobs 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.