Force remove a job from the scheduler
AI agents call force_remove_job to permanently remove resources in Sage MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a job from the scheduler without the ability to undo or recover it. The 'force' qualifier suggests it overrides normal safety checks. This is an irreversible action that cannot be reversed, meeting the definition of Destructive.
From the tool's definition Tool name 'force_remove_job' combined with description 'Force remove a job from the scheduler' — the verb 'force remove' explicitly indicates irreversible deletion of a queued or running job.
Attacks that exploit this kind of access
Force remove a job from the scheduler. It is categorised as a Destructive tool in the Sage MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sage MCP Server MCP server in PolicyLayer and add a rule for force_remove_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 Sage MCP Server. Nothing to install.
force_remove_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 force_remove_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 force_remove_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.
force_remove_job is provided by the Sage MCP Server MCP server (waggle-sensor/sage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →