Repete um job, re-despachando-o com o payload original.
AI agents invoke repetir_job_queue to trigger actions in MCP Officegest. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool re-dispatches a job with its original payload, which constitutes triggering an external operation/execution. Depending on what the original job did (could be financial, destructive, or any side-effecting operation), re-executing it could have significant consequences. Since the job type is unknown but the action is re-dispatching/re-executing, Execute is the most appropriate category.
From the tool's definition Repete um job, re-despachando-o com o payload original
Attacks that exploit this kind of access
Repete um job, re-despachando-o com o payload original. It is categorised as a Execute tool in the MCP Officegest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for repetir_job_queue: 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 MCP Officegest. Nothing to install.
repetir_job_queue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the repetir_job_queue 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 repetir_job_queue. 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.
repetir_job_queue is provided by the MCP Officegest MCP server (rubencodex86/officegest-api-v2-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 →