List all running development servers
AI agents call list_running_servers to retrieve information from DevTools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about running servers without modifying, deleting, or executing any operations. It is a pure read operation that gathers status information. The blast radius is minimal—an AI agent listing servers gains situational awareness but cannot directly harm systems. Severity is low because the information returned is non-sensitive operational metadata in a development context.
From the tool's definition Tool name 'list_running_servers' and description 'List all running development servers' indicate a query/listing operation with no side effects.
Attacks that exploit this kind of access
List all running development servers. It is categorised as a Read tool in the DevTools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevTools MCP Server MCP server in PolicyLayer and add a rule for list_running_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 DevTools MCP Server. Nothing to install.
list_running_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_running_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_running_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_running_servers is provided by the DevTools MCP Server MCP server (shabaraba/devtools-mcp). 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 →