get_slx_runbook
AI agents call get_slx_runbook to retrieve information from RunWhen Platform MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests a query/retrieval operation with no modification or side effects. Despite the empty description, the tool name and server context (direct data access to workspaces and SLXs) indicate this fetches existing runbook information. No evidence of destructive, financial, or execute capabilities.
From the tool's definition Tool name 'get_slx_runbook' indicates a retrieval operation (get prefix). Description is empty, limiting direct evidence, but contextually it retrieves SLX (Service Level Objective/Execute) runbook data from the RunWhen platform workspace, consistent with…
Attacks that exploit this kind of access
get_slx_runbook. It is categorised as a Read tool in the RunWhen Platform MCP MCP Server, which means it retrieves data without modifying state.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for get_slx_runbook: 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 RunWhen Platform MCP. Nothing to install.
get_slx_runbook 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_slx_runbook 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_slx_runbook. 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_slx_runbook is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-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 →