list_agents
AI agents call list_agents to retrieve information from Containerized Strands Agents without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves information about existing agents without modifying, deleting, or executing anything. The empty description prevents higher confidence, but the name strongly suggests a read-only listing operation typical in agent management interfaces. The blast radius is minimal since it only reveals information about agent identities/states without enabling destructive actions.
From the tool's definition Tool name 'list_agents' indicates a retrieval operation with no parameters that would modify state. Combined with sibling tools (get_messages, send_message, stop_agent) that suggest agent management, this is a listing/query function.
Attacks that exploit this kind of access
list_agents. It is categorised as a Read tool in the Containerized Strands Agents MCP Server, which means it retrieves data without modifying state.
Register the Containerized Strands Agents MCP server in PolicyLayer and add a rule for list_agents: 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 Containerized Strands Agents. Nothing to install.
list_agents 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_agents 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_agents. 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_agents is provided by the Containerized Strands Agents MCP server (mkmeral/containerized-strands-agents). 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 →