AI agents call list_agents to retrieve information from Lens without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | string | — | Filter by tags (comma-separated) |
type | string | — | Filter by agent type |
search | string | — | Filter agents by name |
is_active | boolean | — | Filter by active status |
Parameters from the server's own tool schema.
This is a read-only query tool that retrieves and lists agent metadata without modifying, deleting, or executing any operations. It only filters and returns existing data, making it a Read category with low severity.
From the tool's definition Tool name is 'list_agents' and description states 'List agents from the Lens API' with filtering by search, type, is_active, or tags. Explicitly described as a lookup tool to 'see existing agents' before other operations.
Attacks that exploit this kind of access
List agents from the Lens API. Optionally filter by search (name), type, is_active, or tags. Use this to see existing agents before creating new ones (e.g. via Reasoning) or before creating a workflow. It is categorised as a Read tool in the Lens MCP Server, which means it retrieves data without modifying state.
list_agents accepts 4 parameters: tags, type, search, is_active. The full parameter table on this page comes from the server's own tool schema.
Register the Lens 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 Lens. 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 Lens MCP server (lens-mcp-server). 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 →