gemma_worker_cancel_job
A destructive tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/gemma-worker-cancel-job.md
What gemma_worker_cancel_job does on Mapi Agent Memory
AI agents call gemma_worker_cancel_job to permanently remove resources in Mapi Agent Memory, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why gemma_worker_cancel_job is rated Critical
An AI agent that decides to call gemma_worker_cancel_job doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mapi Agent Memory is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs gemma_worker_cancel_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gemma_worker_cancel_job, this is the rule to start with:
gemma_worker_cancel_job is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every gemma_worker_cancel_job call is checked against it from then on.
Questions about gemma_worker_cancel_job
gemma_worker_cancel_job is a destructive tool on the Mapi Agent Memory MCP server. It is categorised as a Destructive tool in the Mapi Agent Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for gemma_worker_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 Mapi Agent Memory. Nothing to install.
gemma_worker_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 gemma_worker_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 gemma_worker_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.
gemma_worker_cancel_job is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
Across the catalogue