Block specific network requests
AI agents invoke block_requests to trigger actions in Pydoll. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool modifies the browser's network behavior by blocking requests, which is an active execution-level operation affecting outbound traffic. It can disrupt page functionality, bypass security checks, or interfere with external services depending on which requests are blocked.
From the tool's definition 'Block specific network requests' — actively intercepts and prevents network traffic from being processed
Documented attack patterns abuse exactly the kind of access block_requests gives an agent:
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 block_requests:
{
"version": "1",
"default": "deny",
"tools": {
"block_requests": {
"limits": [
{
"counter": "block_requests_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}block_requests stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Block specific network requests. It is categorised as a Execute tool in the Pydoll MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pydoll MCP server in PolicyLayer and add a rule for block_requests: 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.
block_requests is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the block_requests 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 block_requests. 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.
block_requests 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.
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.