List all actions in the AgentBridge manifest at a URL.
AI agents call list_actions to retrieve information from AgentBridge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a discovery/introspection tool that retrieves and displays structured metadata about available actions. It has no side effects, does not execute external operations, and does not modify or delete data. It is analogous to API documentation endpoints or schema discovery tools, which are Read category.
From the tool's definition The tool 'list_actions' with description 'List all actions in the AgentBridge manifest at a URL' performs a query/retrieval operation that enumerates available actions from a manifest without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
List all actions in the AgentBridge manifest at a URL. It is categorised as a Read tool in the AgentBridge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AgentBridge MCP Server MCP server in PolicyLayer and add a rule for list_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 AgentBridge MCP Server. Nothing to install.
list_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_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_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_actions is provided by the AgentBridge MCP Server MCP server (marmar9615-cloud/agentbridge-protocol). 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 →