Set the browser viewport size in pixels to simulate different screen resolutions. Use when the user wants to test responsive layouts, simulate a mobile or tablet screen, or change the visible area of the page. For multi-viewport screenshots, use pilot_responsive instead. Parameters: - width: View...
AI agents invoke pilot_resize to trigger actions in Pilot. 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 action (resizing the Chromium viewport), which is an external operation affecting the browser state. It doesn't read data, write persistent data, or destroy anything, but it executes a configuration change on the running browser instance. Severity is low because the blast radius is minimal — it only affects viewport dimensions and is easily reversed.
From the tool's definition Set the browser viewport size in pixels to simulate different screen resolutions
Documented attack patterns abuse exactly the kind of access pilot_resize gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for pilot_resize:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_resize": {
"limits": [
{
"counter": "pilot_resize_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pilot_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.
Set the browser viewport size in pixels to simulate different screen resolutions. Use when the user wants to test responsive layouts, simulate a mobile or tablet screen, or change the visible area of the page. For multi-viewport screenshots, use pilot_responsive instead. Parameters: - width: Viewport width in pixels (e.g., 1280 for desktop, 375 for mobile) - height: Viewport height in pixels (e.g., 720 for desktop, 812 for mobile) Returns: Confirmation with the new viewport dimensions. Errors: None — any valid pixel dimensions are accepted. It is categorised as a Execute tool in the Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_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 Pilot. Nothing to install.
pilot_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 pilot_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 pilot_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.
pilot_resize is provided by the Pilot MCP server (tacosyhorchata/pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 61 Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
61 Pilot tools catalogued and risk-classified — across an index of 42,500+ MCP servers.