List actions (or workers) from all worker-sets
AI agents call list_available_actions to retrieve information from Rockfish MCP Server 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 actions and workers without creating, modifying, deleting, or executing anything. It is a pure information retrieval operation with no side effects, fitting the Read category. The low severity reflects minimal blast radius — listing available actions poses no direct risk to data or systems.
From the tool's definition Tool name is 'list_available_actions' and description states it 'List actions (or workers) from all worker-sets' — a retrieval/enumeration operation with no modification or execution.
Attacks that exploit this kind of access
List actions (or workers) from all worker-sets. It is categorised as a Read tool in the Rockfish MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rockfish MCP Server MCP server in PolicyLayer and add a rule for list_available_actions: 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 Rockfish MCP Server. Nothing to install.
list_available_actions 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_available_actions 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_available_actions. 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_available_actions is provided by the Rockfish MCP Server MCP server (wolfdancer/rockfish-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 →