Lists all third-party developer tools the page exposes for providing runtime information. Third-party developer tools can be called via the
AI agents call list_3p_developer_tools to retrieve information from Chrome Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available developer tools without modifying, executing, or deleting anything. It is purely informational—a read operation that discovers what tools are available. The low severity reflects minimal blast radius: an agent could learn about available tools, but cannot invoke them or affect system state through this listing alone.
From the tool's definition Tool name is 'list_3p_developer_tools' and description states it 'Lists all third-party developer tools the page exposes'. The verb 'lists' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists all third-party developer tools the page exposes for providing runtime information. Third-party developer tools can be called via the. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for list_3p_developer_tools: 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 Chrome Devtools. Nothing to install.
list_3p_developer_tools 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_3p_developer_tools 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_3p_developer_tools. 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_3p_developer_tools is provided by the Chrome Devtools MCP server (zhang77-x/chrpme_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 →