get_location
Return online delivery and U.S. service coverage without exposing a private street address or accepting a location input.
This record as markdown: /tools/com-geezerkeeper-referral-exit-routes/get-location.md
What get_location does on GeezerKeeper Referral Exit Routes and Deadlines
AI agents call get_location to retrieve information from GeezerKeeper Referral Exit Routes and Deadlines without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_location is rated Low
This is a straightforward data retrieval tool that queries service coverage information. It does not accept location input (preventing injection attacks), does not expose PII, and does not modify any state. The low severity reflects minimal blast radius if misused by an agent—worst case, an attacker learns which regions are served.
From the tool's definition Tool description explicitly states it 'Return[s]' information about service coverage and delivery, with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs get_location safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GeezerKeeper Referral Exit Routes and Deadlines, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_location, this is the rule to start with:
get_location 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 GeezerKeeper Referral Exit Routes and Deadlines, apply this rule, and every get_location call is checked against it from then on.
Questions about get_location
Return online delivery and U.S. service coverage without exposing a private street address or accepting a location input. It is categorised as a Read tool in the GeezerKeeper Referral Exit Routes and Deadlines MCP Server, which means it retrieves data without modifying state.
Register the GeezerKeeper Referral Exit Routes and Deadlines MCP server in PolicyLayer and add a rule for get_location: 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 GeezerKeeper Referral Exit Routes and Deadlines. Nothing to install.
get_location 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 get_location 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 get_location. 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.
get_location is provided by the GeezerKeeper Referral Exit Routes and Deadlines MCP server (https://geezerkeeper.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GeezerKeeper Referral Exit Routes and Deadlines, and thousands of servers like it.
Across the catalogue