List available servers (needed for creating bins). Returns server IDs you can use with create_bin.
AI agents call list_servers to retrieve information from RequestBin 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 pure read operation that retrieves and returns information about available servers. It does not create, modify, delete, or execute anything. The act of listing configuration or infrastructure metadata poses minimal security risk on its own, though the resulting server IDs could be used with other tools to create bins or endpoints.
From the tool's definition Tool name is "list_servers" and description states it "List available servers" and "Returns server IDs" — a query operation with no side effects.
Attacks that exploit this kind of access
List available servers (needed for creating bins). Returns server IDs you can use with create_bin. It is categorised as a Read tool in the RequestBin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RequestBin MCP 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 RequestBin MCP 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 RequestBin MCP Server MCP server (requestbin/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 →