AI agents invoke reload to trigger actions in Camoufox Reverse. 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.
Reloading a browser page triggers a new page load and re-executes all init scripts, constituting an active browser operation with external side effects. It's not a simple read, and the re-execution of init scripts means it can trigger arbitrary JavaScript, making it Execute rather than Write.
From the tool's definition Reload the current page, preserving any init scripts
Documented attack patterns abuse exactly the kind of access reload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camoufox Reverse, and nothing reaches the server without passing your rules. This is the rule we recommend for reload:
{
"version": "1",
"default": "deny",
"tools": {
"reload": {
"limits": [
{
"counter": "reload_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}reload 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.
Reload the current page, preserving any init scripts. It is categorised as a Execute tool in the Camoufox Reverse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Camoufox Reverse MCP server in PolicyLayer and add a rule for reload: 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 Camoufox Reverse. Nothing to install.
reload 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 reload 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 reload. 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.
reload is provided by the Camoufox Reverse MCP server (whitenightshadow/camoufox-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Camoufox Reverse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Camoufox Reverse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.