Remove a job by id or name if not running
AI agents call ollama_remove_job to permanently remove resources in Promethean OS MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The verb 'remove' combined with the conditional 'if not running' indicates irreversible deletion of a job. This cannot be undone and represents a destructive operation on system state. While the impact is scoped to a single job rather than critical infrastructure, unauthorized removal of jobs could disrupt workflows.
From the tool's definition Tool name 'ollama_remove_job' with description 'Remove a job by id or name if not running' indicates deletion of a job record.
Attacks that exploit this kind of access
Remove a job by id or name if not running. It is categorised as a Destructive tool in the Promethean OS MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Promethean OS MCP server in PolicyLayer and add a rule for ollama_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 Promethean OS MCP. Nothing to install.
ollama_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 ollama_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 ollama_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.
ollama_remove_job is provided by the Promethean OS MCP server (octave-commons/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 →