Inject a script that runs before every page load.
AI agents invoke inject_init_script 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 arbitrary JavaScript code in the browser context on every page load. It can intercept credentials, modify page behavior, exfiltrate data, or manipulate the DOM persistently. The persistent nature (runs before every page load) increases the blast radius significantly compared to a one-time script execution.
From the tool's definition Inject a script that runs before every page load
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access inject_init_script 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 inject_init_script:
{
"version": "1",
"default": "deny",
"tools": {
"inject_init_script": {
"limits": [
{
"counter": "inject_init_script_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}inject_init_script 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.
Inject a script that runs before every page load. 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 inject_init_script: 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.
inject_init_script 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 inject_init_script 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 inject_init_script. 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.
inject_init_script 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.