Restart an allowed service through SentinelX (/restart).
AI agents invoke sentinel_restart to trigger actions in SentinelX Core MCP. 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 executes a restart operation on services, which is an irreversible state-changing action that affects system availability and operation. While not destructive in the sense of data loss, restarting services can cause downtime, interrupt active operations, and potentially cascade failures.
From the tool's definition Restart an allowed service through SentinelX (/restart) - the tool triggers an external operation (service restart) whose effects depend on which service is targeted as an argument.
Attacks that exploit this kind of access
Restart an allowed service through SentinelX (/restart). It is categorised as a Execute tool in the SentinelX Core MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SentinelX Core MCP server in PolicyLayer and add a rule for sentinel_restart: 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 SentinelX Core MCP. Nothing to install.
sentinel_restart 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 sentinel_restart 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 sentinel_restart. 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.
sentinel_restart is provided by the SentinelX Core MCP server (pensados/sentinelx-core-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 →