Trigger automatic recovery for a failed service using predefined playbooks.
AI agents invoke trigger_auto_recovery to trigger actions in Last Rock 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 external operations with effects dependent on system state and playbook definitions. Recovery operations can restart services, modify configurations, or trigger cascading changes across the infrastructure.
From the tool's definition Tool triggers automatic recovery procedures for failed services using predefined playbooks. The description indicates it executes recovery operations (restart, remediation actions) on live infrastructure.
Attacks that exploit this kind of access
Trigger automatic recovery for a failed service using predefined playbooks. It is categorised as a Execute tool in the Last Rock MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Last Rock MCP server in PolicyLayer and add a rule for trigger_auto_recovery: 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 Last Rock MCP. Nothing to install.
trigger_auto_recovery 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 trigger_auto_recovery 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 trigger_auto_recovery. 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.
trigger_auto_recovery is provided by the Last Rock MCP server (itsablabla/lastrock-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 →