Low Risk

browser_close

browser_close

How to control browser_close ↓

What browser_close does on Amazon Translate MCP Server

AI agents call browser_close as a supporting operation in Amazon Translate MCP Server workflows.

Low Risk

Why browser_close needs a policy

The description is completely empty, making confident classification impossible. The tool name 'browser_close' suggests closing a browser session (Execute category), but this tool appears out of place on an Amazon Translate server. Without a description, confidence is very low and the safest classification given the ambiguity and low blast radius of closing a browser is Other, with reduced confidence.

From the tool's definition Tool name is 'browser_close' but description is empty and uninformative; the tool name alone suggests closing a browser instance, which is an Execute-level action, but it is anomalous on an Amazon Translate MCP server

Documented attack patterns abuse exactly the kind of access browser_close gives an agent:

How to control browser_close

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Translate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_close:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_close": {
      "limits": [
        {
          "counter": "browser_close_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_close gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Translate MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_close

What does the browser_close tool do? +

browser_close. It is categorised as a Other tool in the Amazon Translate MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on browser_close? +

Register the Amazon Translate 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 Translate MCP Server. Nothing to install.

What risk level is browser_close? +

browser_close is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_close? +

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.

How do I block browser_close completely? +

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.

What MCP server provides browser_close? +

browser_close is provided by the Amazon Translate MCP Server MCP server (awslabs.amazon-translate-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Translate MCP Server tool call.

Start from Amazon Translate MCP 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.

805 Amazon Translate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.