Restart a server
AI agents invoke restart_server to trigger actions in Ploi MCP Server. 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.
Restarting a server is an Execute action—it runs a command/operation on external infrastructure whose consequences depend on the argument (which server). While disruptive, it is not Destructive (data is not deleted) and not Financial. The high severity reflects potential service downtime and business impact if misused by an AI agent on the wrong server.
From the tool's definition Tool name 'restart_server' and description 'Restart a server' indicate execution of a server restart operation, which triggers external infrastructure changes with effects dependent on which server argument is provided.
Attacks that exploit this kind of access
Restart a server. It is categorised as a Execute tool in the Ploi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for restart_server: 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 Ploi MCP Server. Nothing to install.
restart_server 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 restart_server 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 restart_server. 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.
restart_server is provided by the Ploi MCP Server MCP server (sudanese/ploi-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 →