Low Risk

fetch_domain_commands

Fetch all possible commands available for the current domain from Chrome DevTools Protocol

How to control fetch_domain_commands ↓

What fetch_domain_commands does on Pydoll

AI agents call fetch_domain_commands to retrieve information from Pydoll without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fetch_domain_commands needs a policy

This is a Read operation—it queries and retrieves information about available commands from the Chrome DevTools Protocol without performing actions, modifying data, or causing side effects. It is not Write (no modification), Execute (no action invocation), Destructive (no deletion), or Financial (no money movement).

From the tool's definition Tool fetches and retrieves commands available from Chrome DevTools Protocol without executing them. The verb 'Fetch' and description 'Fetch all possible commands' indicate data retrieval.

Documented attack patterns abuse exactly the kind of access fetch_domain_commands gives an agent:

How to control fetch_domain_commands

PolicyLayer is an MCP gateway — it sits between your AI agents and Pydoll, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_domain_commands:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_domain_commands": {}
  }
}

fetch_domain_commands is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Pydoll — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_domain_commands

What does the fetch_domain_commands tool do? +

Fetch all possible commands available for the current domain from Chrome DevTools Protocol. It is categorised as a Read tool in the Pydoll MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_domain_commands? +

Register the Pydoll MCP server in PolicyLayer and add a rule for fetch_domain_commands: 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 Pydoll. Nothing to install.

What risk level is fetch_domain_commands? +

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

Can I rate-limit fetch_domain_commands? +

Yes. Add a rate_limit block to the fetch_domain_commands 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 fetch_domain_commands completely? +

Set action: deny in the PolicyLayer policy for fetch_domain_commands. 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 fetch_domain_commands? +

fetch_domain_commands is provided by the Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pydoll tool call.

Start from Pydoll, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.