Find URL/port for a process by name
AI agents call find_process_url 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 queries process metadata to return URL/port information. It performs no modifications, deletions, executions, or financial operations. The action is informational and read-only, consistent with tools like 'list_running_servers' and 'detailed_process_list' on the same server.
From the tool's definition Tool name 'find_process_url' and description 'Find URL/port for a process by name' indicate a lookup/query operation that retrieves process network information without modification or side effects.
Attacks that exploit this kind of access
Find URL/port for a process by name. 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 find_process_url: 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.
find_process_url 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 find_process_url 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 find_process_url. 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.
find_process_url 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 →