camoufox_server
Start, close, or check status of a Camoufox anti-detect server.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/camoufox-server.md
What camoufox_server does on Jshookmcp
AI agents invoke camoufox_server to trigger actions in Jshookmcp. 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.
Why camoufox_server is rated High
Launches external processes with state-changing effects; anti-detect capability suggests evasion or obfuscation potential.
From the tool's definition Start, close, check status of Camoufox anti-detect server
Attacks that exploit this kind of access
The rule that runs camoufox_server safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For camoufox_server, this is the rule to start with:
camoufox_server 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every camoufox_server call is checked against it from then on.
Questions about camoufox_server
Start, close, or check status of a Camoufox anti-detect server. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jshook MCP server in PolicyLayer and add a rule for camoufox_server: 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 Jshookmcp. Nothing to install.
camoufox_server 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 camoufox_server 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 camoufox_server. 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.
camoufox_server is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
Across the catalogue