Random mouse movements over a duration — builds up mouse history before action (CF/DataDome behavior analysis).
AI agents invoke mouse_drift to trigger actions in MCP Camoufox. 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 executes browser-level mouse movement automation designed to simulate human behavior and evade bot detection systems. It triggers external browser operations (mouse movements) and is specifically designed to bypass security controls like Cloudflare and DataDome.
From the tool's definition Random mouse movements over a duration — builds up mouse history before action (CF/DataDome behavior analysis)
Documented attack patterns abuse exactly the kind of access mouse_drift gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for mouse_drift:
{
"version": "1",
"default": "deny",
"tools": {
"mouse_drift": {
"limits": [
{
"counter": "mouse_drift_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mouse_drift 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.
Random mouse movements over a duration — builds up mouse history before action (CF/DataDome behavior analysis). It is categorised as a Execute tool in the MCP Camoufox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for mouse_drift: 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 MCP Camoufox. Nothing to install.
mouse_drift 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 mouse_drift 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 mouse_drift. 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.
mouse_drift is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Camoufox, 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.
102 MCP Camoufox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.