gemma_worker_reject_job
A write tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/gemma-worker-reject-job.md
What gemma_worker_reject_job does on Mapi Agent Memory
AI agents use gemma_worker_reject_job to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.
Why gemma_worker_reject_job is rated Medium
The tool appears to reject or cancel a job, which is a state modification action. Without a description, it is unclear whether this rejection is reversible (Write) or permanent (Destructive).
From the tool's definition Tool name contains 'reject_job' which indicates modifying job state/status; no description provided to determine if this is reversible or irreversible.
Attacks that exploit this kind of access
The rule that runs gemma_worker_reject_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_reject_job, this is the rule to start with:
gemma_worker_reject_job stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every gemma_worker_reject_job call is checked against it from then on.
Questions about gemma_worker_reject_job
gemma_worker_reject_job is a write tool on the Mapi Agent Memory MCP server. It is categorised as a Write tool in the Mapi Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for gemma_worker_reject_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_reject_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gemma_worker_reject_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_reject_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_reject_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.
This server
Across the catalogue