Agenda o reinício de um supervisor, ciclando todos os seus workers.
AI agents invoke reiniciar_supervisor 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 schedules a restart of a supervisor process, cycling all its workers. This is an operational action that triggers external process management behavior — it doesn't merely read or write data, but executes a system-level operation (process restart/cycle) whose effects depend on the target supervisor. Misuse could disrupt running services by taking down all workers, making it high severity.
From the tool's definition Agenda o reinício de um supervisor, ciclando todos os seus workers
Attacks that exploit this kind of access
Agenda o reinício de um supervisor, ciclando todos os seus workers. 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 reiniciar_supervisor: 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.
reiniciar_supervisor 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 reiniciar_supervisor 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 reiniciar_supervisor. 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.
reiniciar_supervisor 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 →