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

reiniciar_supervisor

Agenda o reinício de um supervisor, ciclando todos os seus workers.

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/reiniciar-supervisor.md

What reiniciar_supervisor does on MCP Officegest

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.

Why reiniciar_supervisor is rated High

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

Questions about reiniciar_supervisor

What does the reiniciar_supervisor tool do? +

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.

How do I enforce a policy on reiniciar_supervisor? +

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.

What risk level is reiniciar_supervisor? +

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

Can I rate-limit reiniciar_supervisor? +

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.

How do I block reiniciar_supervisor completely? +

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.

What MCP server provides reiniciar_supervisor? +

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.

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.