Get detailed process information with CPU, memory usage
AI agents call detailed_process_list 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 and reports metrics about running processes (CPU, memory usage). It has no side effects, does not modify state, does not execute code or commands, and does not delete data. It is purely informational and falls squarely within the Read category.
From the tool's definition Tool description states 'Get detailed process information with CPU, memory usage' — a retrieval operation that queries system process data without modification or execution.
Attacks that exploit this kind of access
Get detailed process information with CPU, memory usage. 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 detailed_process_list: 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.
detailed_process_list 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 detailed_process_list 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 detailed_process_list. 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.
detailed_process_list 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 →