Low Risk

maps_place_details

Get detailed information about a specific place

How to control maps_place_details ↓

What maps_place_details does on MCP-Brave-Search

AI agents call maps_place_details to retrieve information from MCP-Brave-Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why maps_place_details needs a policy

This tool retrieves place information without modifying, executing, or destroying data. It has minimal blast radius even if an AI agent requests details about arbitrary places—the worst outcome is exposure of publicly available location information. Classified as Read with low severity.

From the tool's definition Tool name 'maps_place_details' and description 'Get detailed information about a specific place' indicate a retrieval operation. The verb 'Get' and the absence of any modification, deletion, or execution language confirm read-only behavior.

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

How to control maps_place_details

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Brave-Search, and nothing reaches the server without passing your rules. This is the rule we recommend for maps_place_details:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "maps_place_details": {}
  }
}

maps_place_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP-Brave-Search — 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about maps_place_details

What does the maps_place_details tool do? +

Get detailed information about a specific place. It is categorised as a Read tool in the MCP-Brave-Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on maps_place_details? +

Register the MCP-Brave-Search MCP server in PolicyLayer and add a rule for maps_place_details: 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 MCP-Brave-Search. Nothing to install.

What risk level is maps_place_details? +

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

Can I rate-limit maps_place_details? +

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

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

maps_place_details is provided by the MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-Brave-Search tool call.

Start from MCP-Brave-Search, 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.

59 MCP-Brave-Search 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.