google-maps.place_types
List supported Google Maps place type values for search filters. Returns place_types as a string array. Use a value with place_type on google-maps.search or google-maps.nearby_search. Cost = 1 token.
This record as markdown: /tools/io-github-vee3io-vee3/google-maps.place-types.md
What google-maps.place_types does on Vee3
AI agents call google-maps.place_types to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why google-maps.place_types is rated Low
This tool retrieves reference data (enumeration of valid place type values) with no side effects. It is purely informational and read-only, used to support other search operations. The low severity reflects minimal blast radius—misuse could only waste API tokens or inform an agent of valid filter options.
From the tool's definition Tool description states it 'List[s] supported Google Maps place type values' and 'Returns place_types as a string array'. No creation, modification, deletion, code execution, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs google-maps.place_types safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-maps.place_types, this is the rule to start with:
google-maps.place_types is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every google-maps.place_types call is checked against it from then on.
Questions about google-maps.place_types
List supported Google Maps place type values for search filters. Returns place_types as a string array. Use a value with place_type on google-maps.search or google-maps.nearby_search. Cost = 1 token. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
Register the Vee3 MCP server in PolicyLayer and add a rule for google-maps.place_types: 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 Vee3. Nothing to install.
google-maps.place_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the google-maps.place_types 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.
Set action: deny in the PolicyLayer policy for google-maps.place_types. 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.
google-maps.place_types is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue