GOOGLESUPER_NEARBY_SEARCH

Searches for places (e.g., restaurants, parks) within a specified circular area, with options to filter by place types and customize the returned fields and number of results.

SERVERGoogle Super SOURCEgooglesuper

Low RISK CLASS

Category Read

Parameters 70 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-nearby-search.md

WHAT IT DOES

What GOOGLESUPER_NEARBY_SEARCH does on Google Super

AI agents call GOOGLESUPER_NEARBY_SEARCH to retrieve information from Google Super 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
`radius`	number	—	Radius of the circular search area in meters.
`latitude`	number	—	Latitude coordinate of the search center in decimal degrees.
`fieldMask`	string	—	Comma-separated list of place fields for the response (e.g., 'places.displayName,places.formattedAddress'); use '*' for all fields.
`longitude`	number	—	Longitude coordinate of the search center in decimal degrees.
`excludedTypes`	array	—	Place types to exclude (e.g., 'cafe', 'store'); results matching any of these types are omitted. For supported types, see Google Maps Places API documentation.
`includedTypes`	array	—	Place types to include (e.g., 'restaurant', 'park'); results will match at least one of these types. For supported types, see Google Maps Places API documentati
`maxResultCount`	integer	—	Maximum number of search results to return (up to 20); the actual count may be lower.

Parameters from the server's own tool schema.

RISK

Why GOOGLESUPER_NEARBY_SEARCH is rated Low

This is a search/query operation that retrieves location-based information about places. It has no side effects, does not modify any data, does not execute commands, does not delete anything, and involves no financial transactions. The tool is read-only, making it the lowest-risk category. Severity is low because location search data is generally non-sensitive and misuse would not create significant harm.

From the tool's definition Tool performs 'Searches for places' with 'options to filter by place types and customize the returned fields and number of results' — pure data retrieval with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GOOGLESUPER_NEARBY_SEARCH safely

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

GOOGLESUPER_NEARBY_SEARCH Allowed

GOOGLESUPER_NEARBY_SEARCH 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": {
    "GOOGLESUPER_NEARBY_SEARCH": {}
  }
}

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

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

FAQ

Questions about GOOGLESUPER_NEARBY_SEARCH

What does the GOOGLESUPER_NEARBY_SEARCH tool do? +

Searches for places (e.g., restaurants, parks) within a specified circular area, with options to filter by place types and customize the returned fields and number of results. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.

What parameters does GOOGLESUPER_NEARBY_SEARCH accept? +

GOOGLESUPER_NEARBY_SEARCH accepts 7 parameters: radius, latitude, fieldMask, longitude, excludedTypes, includedTypes, maxResultCount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_NEARBY_SEARCH? +

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

What risk level is GOOGLESUPER_NEARBY_SEARCH? +

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

Can I rate-limit GOOGLESUPER_NEARBY_SEARCH? +

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

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

GOOGLESUPER_NEARBY_SEARCH is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Google Super, and thousands of servers like it.

This server

All 200 Google Super tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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