browser_close
AI agents call browser_close as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty, making classification difficult. The name 'browser_close' suggests closing a browser, which could be an Execute action, but given the context of an Amazon MQ server and the lack of description, confidence is very low. It seems out of place on an MQ broker management server, possibly a utility or cleanup action.
From the tool's definition Tool name is 'browser_close' but description is empty and uninformative; the name suggests closing a browser instance.
Attacks that exploit this kind of access
browser_close. 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_close: 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_close 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_close 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_close. 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_close 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.