browser_close · Amazon ElastiCache Memcached MCP Server MCP

WHAT IT DOES

What browser_close does on Amazon ElastiCache Memcached MCP Server

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

WHY IT NEEDS A POLICY

Why browser_close needs a policy

With an empty description, classification is uncertain. The name 'browser_close' suggests closing a browser instance (an Execute-level action), but given the mismatch with the server context (ElastiCache Memcached) and lack of description, confidence is very low. Defaulting to Other with low severity pending more information.

From the tool's definition Tool name is 'browser_close' but the description is empty and uninformative. The tool appears on an Amazon ElastiCache Memcached MCP server, which is an unusual context for a browser-related tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_close Rate-limited

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

View as policy code

policy.json

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

SET A RULE FOR THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Amazon ElastiCache Memcached MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_close

What does the browser_close tool do? +

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

How do I enforce a policy on browser_close? +

Register the Amazon ElastiCache Memcached 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 ElastiCache Memcached 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 ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.