Visit innocuous public sites (Google, Wikipedia) to build browsing history before targeting protected site. Helps with CF/DataDome IP scoring.
AI agents invoke session_warmup 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 automated browser navigation and history-building actions to evade bot detection systems. While superficially innocuous (visiting public sites), the intent and effect are to manipulate detection mechanisms to enable subsequent unauthorized access to protected sites. The tool's purpose is specifically to prepare for bypassing security controls on 'protected site[s]'.
From the tool's definition Tool description states it 'Visit innocuous public sites' and 'build browsing history' to help 'with CF/DataDome IP scoring' - these are automated browser actions that trigger external operations (HTTP requests, page loads, history manipulation).
Documented attack patterns abuse exactly the kind of access session_warmup 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 session_warmup:
{
"version": "1",
"default": "deny",
"tools": {
"session_warmup": {
"limits": [
{
"counter": "session_warmup_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}session_warmup 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.
Visit innocuous public sites (Google, Wikipedia) to build browsing history before targeting protected site. Helps with CF/DataDome IP scoring. 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 session_warmup: 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.
session_warmup 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 session_warmup 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 session_warmup. 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.
session_warmup 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.