Press a key on the keyboard.
AI agents invoke browser_press_key to trigger actions in 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 triggers a browser keyboard action, which is an external browser operation. Pressing keys can submit forms, trigger shortcuts, or activate UI elements — effects depend on browser state and arguments. It falls under Execute as it performs an action in an external system (the browser) with context-dependent effects.
From the tool's definition Press a key on the keyboard
Documented attack patterns abuse exactly the kind of access browser_press_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_press_key:
{
"version": "1",
"default": "deny",
"tools": {
"browser_press_key": {
"limits": [
{
"counter": "browser_press_key_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_press_key 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.
Press a key on the keyboard. It is categorised as a Execute tool in the Camoufox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Camoufox MCP server in PolicyLayer and add a rule for browser_press_key: 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. Nothing to install.
browser_press_key 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 browser_press_key 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 browser_press_key. 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.
browser_press_key is provided by the Camoufox MCP server (rlgrpe/camoufox-mcp-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 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.
22 Camoufox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.