Simulate different network conditions
AI agents invoke throttle_network 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 actively modifies the browser's network behavior by throttling/simulating network conditions (e.g., slow 3G, offline). It triggers an external operation that changes the runtime environment, making it an Execute-category tool. Misuse could disrupt network access or cause dependent operations to fail/behave unexpectedly.
From the tool's definition Simulate different network conditions
Documented attack patterns abuse exactly the kind of access throttle_network 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 throttle_network:
{
"version": "1",
"default": "deny",
"tools": {
"throttle_network": {
"limits": [
{
"counter": "throttle_network_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}throttle_network 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.
Simulate different network conditions. 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 throttle_network: 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.
throttle_network 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 throttle_network 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 throttle_network. 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.
throttle_network 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.