AI agents call list_playbooks to retrieve information from Cawskills without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available playbooks without modifying, executing, or deleting any data. It is a straightforward listing/enumeration operation typical of Read category tools.
From the tool's definition Tool name 'list_playbooks' and description 'List all available ClawSkills workflow playbooks' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all available ClawSkills workflow playbooks. It is categorised as a Read tool in the Cawskills MCP Server, which means it retrieves data without modifying state.
Register the Cawskills MCP server in PolicyLayer and add a rule for list_playbooks: 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 Cawskills. Nothing to install.
list_playbooks 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 list_playbooks 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 list_playbooks. 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.
list_playbooks is provided by the Cawskills MCP server (shanksg/clawskills). 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 →