Get a structured validation playbook with step-by-step instructions. Playbooks provide ordered steps to validate infrastructure changes like Helm charts, database migrations, Kubernetes upgrades, and more.
AI agents call get_playbook to retrieve information from Agent Zone without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-existing playbook documents that provide validation guidance. It is informational and read-only with no side effects on infrastructure, data modification, or financial impact. The 'Get' verb and retrieval-focused description confirm this is a Read category tool. Severity is low as misuse would only expose instructional documentation without enabling unauthorized actions on systems.
From the tool's definition Tool name 'get_playbook' and description 'Get a structured validation playbook with step-by-step instructions' indicates retrieval of existing documentation/guidance.
Attacks that exploit this kind of access
Get a structured validation playbook with step-by-step instructions. Playbooks provide ordered steps to validate infrastructure changes like Helm charts, database migrations, Kubernetes upgrades, and more. It is categorised as a Read tool in the Agent Zone MCP Server, which means it retrieves data without modifying state.
Register the Agent Zone MCP server in PolicyLayer and add a rule for get_playbook: 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 Agent Zone. Nothing to install.
get_playbook is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_playbook 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 get_playbook. 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.
get_playbook is provided by the Agent Zone MCP server (statherm/agent-zone-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 →