AI agents invoke resize to trigger actions in PlayMCP Browser Automation Server. 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.
Resizing the browser viewport is a browser control action that affects the running Playwright session. It doesn't read data, write persistent data, or cause destructive/financial effects, but it does execute an operation against an external browser process. Severity is low as the blast radius of misuse is minimal — it only changes the viewport dimensions.
From the tool's definition 'Resize the browser viewport' — triggers an external browser operation that changes the state of the running browser session
Documented attack patterns abuse exactly the kind of access resize gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PlayMCP Browser Automation Server, and nothing reaches the server without passing your rules. This is the rule we recommend for resize:
{
"version": "1",
"default": "deny",
"tools": {
"resize": {
"limits": [
{
"counter": "resize_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}resize 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.
Resize the browser viewport. It is categorised as a Execute tool in the PlayMCP Browser Automation Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PlayMCP Browser Automation Server MCP server in PolicyLayer and add a rule for resize: 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 PlayMCP Browser Automation Server. Nothing to install.
resize 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 resize 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 resize. 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.
resize is provided by the PlayMCP Browser Automation Server MCP server (jomon003/playmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PlayMCP Browser Automation Server, 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.
38 PlayMCP Browser Automation Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.