List all server names configured in a specific client
AI agents call list_servers to retrieve information from MCP Client Configuration Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing MCP server configurations. It performs no write, delete, code execution, or financial operations. The information exposed (server names) is configuration metadata that helps an AI agent understand available integrations, but misuse would only affect visibility, not system integrity or data safety. This is a standard read operation with minimal blast radius.
From the tool's definition Tool description states 'List all server names configured in a specific client' — a query operation that retrieves configuration data without modification.
Attacks that exploit this kind of access
List all server names configured in a specific client. It is categorised as a Read tool in the MCP Client Configuration Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Client Configuration Server MCP server in PolicyLayer and add a rule for list_servers: 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 MCP Client Configuration Server. Nothing to install.
list_servers 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_servers 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_servers. 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_servers is provided by the MCP Client Configuration Server MCP server (landicefu/mcp-client-configuration-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 →