Trigger a rolling restart of a Kubernetes deployment.
AI agents invoke ralph_hero__sre__rollout_restart to trigger actions in Ralph Hero. 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.
Rolling restarts of Kubernetes deployments are Execute-category operations because they trigger infrastructure changes through an external system. While the action is theoretically reversible (restarting is not destructive of data), it causes immediate operational impact: service interruptions, pod terminations, and state changes in a production environment.
From the tool's definition Tool name contains 'rollout_restart' and description states 'Trigger a rolling restart of a Kubernetes deployment.' This is an explicit Execute action that triggers external operations (Kubernetes cluster state changes) whose effects depend on arguments…
Attacks that exploit this kind of access
Trigger a rolling restart of a Kubernetes deployment. It is categorised as a Execute tool in the Ralph Hero MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__sre__rollout_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 Ralph Hero. Nothing to install.
ralph_hero__sre__rollout_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 ralph_hero__sre__rollout_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 ralph_hero__sre__rollout_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.
ralph_hero__sre__rollout_restart is provided by the Ralph Hero MCP server (ralph-hero-mcp-server). 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 →