AI agents invoke set_viewport_size 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 changes the browser's viewport dimensions, which is a browser execution action affecting the rendering environment. It's not purely reading data, nor is it writing persistent data or destructive. It falls under Execute as it triggers an external browser operation (viewport configuration change). Blast radius is low since it only affects display dimensions.
From the tool's definition Set viewport width and height — modifies browser state/configuration
Documented attack patterns abuse exactly the kind of access set_viewport_size 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 set_viewport_size:
{
"version": "1",
"default": "deny",
"tools": {
"set_viewport_size": {
"limits": [
{
"counter": "set_viewport_size_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_viewport_size 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.
Set viewport width and height. 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 set_viewport_size: 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.
set_viewport_size 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 set_viewport_size 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 set_viewport_size. 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.
set_viewport_size 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.