list_3p_developer_tools

Lists all third-party developer tools the page exposes for providing runtime information. Third-party developer tools can be called via the

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/list-3p-developer-tools.md

WHAT IT DOES

What list_3p_developer_tools does on Chrome Devtools

AI agents call list_3p_developer_tools to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_3p_developer_tools is rated Low

Queries and enumerates available tools without modifying data or triggering operations.

From the tool's definition Lists all third-party developer tools the page exposes

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_3p_developer_tools safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_3p_developer_tools, this is the rule to start with:

list_3p_developer_tools Allowed

list_3p_developer_tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_3p_developer_tools": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every list_3p_developer_tools call is checked against it from then on.

FAQ

Questions about list_3p_developer_tools

What does the list_3p_developer_tools tool do? +

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.

How do I enforce a policy on list_3p_developer_tools? +

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.

What risk level is list_3p_developer_tools? +

list_3p_developer_tools is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_3p_developer_tools? +

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.

How do I block list_3p_developer_tools completely? +

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.

What MCP server provides list_3p_developer_tools? +

list_3p_developer_tools is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →