New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

repetir_job_queue

Repete um job, re-despachando-o com o payload original.

SERVERMCP Officegest SOURCErubencodex86/officegest-api-v2-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rubencodex86-officegest-api-v2-mcp/repetir-job-queue.md

What repetir_job_queue does on MCP Officegest

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.

Why repetir_job_queue is rated High

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

Questions about repetir_job_queue

What does the repetir_job_queue tool do? +

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.

How do I enforce a policy on repetir_job_queue? +

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.

What risk level is repetir_job_queue? +

repetir_job_queue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit repetir_job_queue? +

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.

How do I block repetir_job_queue completely? +

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.

What MCP server provides repetir_job_queue? +

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.

More on MCP Officegest, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Officegest's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.