browser_resize
AI agents call browser_resize as a supporting operation in Amazon SageMaker AI MCP Server workflows.
With an empty description, classification relies solely on the name. 'browser_resize' implies a browser viewport resize operation — a benign UI action. However, the low confidence reflects uncertainty due to lack of description. It doesn't clearly fit Read, Write, Execute, Destructive, or Financial categories; a browser resize is typically a cosmetic/display-only operation.
From the tool's definition Tool name is 'browser_resize' with empty description. The name suggests resizing a browser window, which is a UI/display action with no obvious data read/write/execute semantics.
Attacks that exploit this kind of access
browser_resize. It is categorised as a Other tool in the Amazon SageMaker AI MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon SageMaker AI 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 SageMaker AI 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 SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.