Apply comprehensive evasion techniques
AI agents invoke evade_detection 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 applies techniques to evade browser fingerprinting, bot detection, and security measures. It triggers external operations (modifying browser behavior to circumvent security controls), placing it in the Execute category. The severity is high because misuse could enable unauthorized access to protected systems, bypass anti-fraud mechanisms, or facilitate malicious automation at scale.
From the tool's definition 'Apply comprehensive evasion techniques' combined with server description mentioning 'captcha bypass' and sibling tools like bypass_cloudflare and bypass_recaptcha
Documented attack patterns abuse exactly the kind of access evade_detection 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 evade_detection:
{
"version": "1",
"default": "deny",
"tools": {
"evade_detection": {
"limits": [
{
"counter": "evade_detection_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}evade_detection 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.
Apply comprehensive evasion techniques. 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 evade_detection: 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.
evade_detection 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 evade_detection 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 evade_detection. 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.
evade_detection 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.