Low Risk

browser_network_requests

browser_network_requests

How to control browser_network_requests ↓

What browser_network_requests does on Amazon Location Service MCP Server

AI agents call browser_network_requests as a supporting operation in Amazon Location Service MCP Server workflows.

Low Risk

Why browser_network_requests needs a policy

The description is empty, so the classification is based solely on the tool name. 'browser_network_requests' suggests capturing or monitoring network requests in a browser context, which could be a Read operation. However, given the lack of description and the somewhat unusual context (an AWS Location Service MCP server), confidence is very low.

From the tool's definition Tool name is 'browser_network_requests' but description is empty or uninformative.

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

How to control browser_network_requests

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

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

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

  1. Create a free account and register Amazon Location Service 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_network_requests

What does the browser_network_requests tool do? +

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

How do I enforce a policy on browser_network_requests? +

Register the Amazon Location Service MCP Server MCP server in PolicyLayer and add a rule for browser_network_requests: 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 Location Service MCP Server. Nothing to install.

What risk level is browser_network_requests? +

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

Can I rate-limit browser_network_requests? +

Yes. Add a rate_limit block to the browser_network_requests 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_network_requests completely? +

Set action: deny in the PolicyLayer policy for browser_network_requests. 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_network_requests? +

browser_network_requests is provided by the Amazon Location Service MCP Server MCP server (awslabs.aws-location-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 Location Service MCP Server tool call.

Start from Amazon Location Service 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 Location Service 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.