browser_resize
AI agents call browser_resize as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty, providing no actionable information. The tool name 'browser_resize' suggests resizing a browser window, which is a benign UI operation with no obvious read/write/execute/destructive/financial implications. However, the very low confidence reflects the lack of description and the unexpected presence of a browser resize tool on an Amazon MQ server.
From the tool's definition Tool name is 'browser_resize' and the description is empty or uninformative. The name suggests a UI/browser window resize operation.
Attacks that exploit this kind of access
browser_resize. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for browser_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 Amazon MQ MCP Server. Nothing to install.
browser_resize is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser_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 browser_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.
browser_resize is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.