MCP Server Policy
GOOGLE MAPS MCP POLICY
Enforce policies on every tool call to the Google Maps MCP Server. 7 tools listed, categorised, and ready for rules.
GET STARTED
Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Google Maps.
# Download policy scaffold
curl -o google-maps.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/google-maps.yaml
# Run with Intercept
intercept --policy google-maps.yaml -- npx -y @@modelcontextprotocol/server-google-maps Server documentation: https://github.com/modelcontextprotocol/servers-archived/tree/main/src/google-maps
READ TOOLS
7POLICY YAML
This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.
version: "1"
description: "Policy for @modelcontextprotocol/server-google-maps"
default: "allow"
tools:
maps_geocode:
rules: []
maps_reverse_geocode:
rules: []
maps_search_places:
rules: []
maps_place_details:
rules: []
maps_distance_matrix:
rules: []
maps_elevation:
rules: []
maps_directions:
rules: [] FREQUENTLY ASKED QUESTIONS
What tools does the Google Maps MCP server expose?
The Google Maps MCP Server exposes 7 tools across 1 categories: Read. Each tool can be individually controlled with Intercept policies.
How do I enforce policies on Google Maps?
Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Google Maps MCP server. Every tool call is evaluated against your YAML policy before execution.
Is the Google Maps policy free to use?
Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.
ENFORCE POLICIES ON GOOGLE MAPS
Open source. One binary. Zero dependencies.