AI agents call list_agents to retrieve information from Snak without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays agent configurations without creating, modifying, or deleting data. It is a pure query operation with no side effects. The optional filtering does not change the read-only nature of the operation. Severity is low because disclosure of agent configurations carries minimal immediate risk compared to write, execute, or destructive operations.
From the tool's definition Tool description states: "List/show/get all agent configurations with optional filtering." The verbs 'list', 'show', and 'get' are characteristic of read-only retrieval operations. No modification, deletion, or execution is described.
Attacks that exploit this kind of access
List/show/get all agent configurations with optional filtering. Use when user wants to see multiple agents, all agents, or find agents matching certain criteria. It is categorised as a Read tool in the Snak MCP Server, which means it retrieves data without modifying state.
Register the Snak 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 Snak. 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 Snak MCP server (kasarlabs/snak). 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 →