resolve_names

SERVERMcp SOURCEhttps://mapstools.googleapis.com/mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-mapstools-mcp/resolve-names.md

WHAT IT DOES

What resolve_names does on Mcp

AI agents call resolve_names to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`queries`	array	Yes	Required. A list of location queries to be resolved. You may specify up to 20 queries.
`regionCode`	string	—	Optional. An optional region code to bias the resolution results. If specified, the resolution results will be biased towards the entities that are in or near t
`locationBias`	object	—	Optional. An optional region to bias the resolution results. If specified, the resolution results will be biased towards the entities that are closer to this re

Parameters from the server's own tool schema.

RISK

Why resolve_names is rated Low

This tool only reads/looks up data by converting location names or addresses into Place IDs. It has no side effects, does not modify any data, and only retrieves canonical identifiers from Google Maps.

From the tool's definition Resolves a batch list of specific location queries (landmark names or exact addresses) into canonical Google Maps Place IDs

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs resolve_names safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resolve_names, this is the rule to start with:

resolve_names Allowed

resolve_names is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_names": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every resolve_names call is checked against it from then on.

FAQ

Questions about resolve_names

What does the resolve_names tool do? +

Resolves a batch list of specific location queries (landmark names or exact addresses) into canonical Google Maps Place IDs. Input Requirements (CRITICAL): 1. queries (array of objects - MANDATORY): A list of location queries to resolve. You may specify up to 20 queries. * Each query object must have: * text (string - MANDATORY): The text query representing a specific place name or address to resolve. * Examples: 'Googleplex, Mountain View, CA', '1600 Amphitheatre Pkwy, Mountain View, CA', 'Eiffel Tower, Paris'. 2. location_bias (object - OPTIONAL): Use this to prioritize results near a specific geographic area. * Format: {"viewport": {"low": {"latitude": [value], "longitude": [value]}, "high": {"latitude": [value], "longitude": [value]}}} 3. region_code (string - OPTIONAL): The Unicode CLDR region code (two-letter country code, e.g., US, CA) of the user to bias the results. Instructions for Tool Call: * Specificity (CRITICAL): Queries must represent a specific place name or address. General searches like 'restaurants' or chain names like 'Starbucks' are not supported. * Do NOT call this tool if the downstream tools you plan to invoke already accept raw address or place name strings directly. Error Handling (CRITICAL): * This is a batch processing tool. A request might return "mixed results" (e.g. some queries resolve successfully while others fail). * The output list of results is guaranteed to map 1:1 with the input queries indices. A failed query will result in an empty Result message (no entity is set) at its corresponding index in the results list. * You MUST check the failed_requests map field in the response to identify which specific query index failed. The key of failed_requests represents the 0-based index of the failed query in the request. Do not assume the entire batch call failed because of a partial failure. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does resolve_names accept? +

resolve_names accepts 3 parameters: queries, regionCode, locationBias. Required: queries. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_names? +

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

What risk level is resolve_names? +

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

Can I rate-limit resolve_names? +

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

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

resolve_names is provided by the MCP server (https://mapstools.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 5 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →