# get_location

Return online delivery and U.S. service coverage without exposing a private street address or accepting a location input.

Agent View of the PolicyLayer registry record for `get_location`. HTML page: https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/get-location

## Facts

- Tool: `get_location`
- Server: GeezerKeeper Referral Exit Routes and Deadlines (`https://geezerkeeper.com/mcp`) — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes.md
- Homepage: https://github.com/https://geezerkeeper.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_location",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool description explicitly states it 'Return[s]' information about service coverage and delivery, with no modification, deletion, or execution capability."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GeezerKeeper Referral Exit Routes and Deadlines:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_location": {}
  }
}
```

## Other tools on GeezerKeeper Referral Exit Routes and Deadlines (6)

- `choose_private_workflow` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/choose-private-workflow.md
- `get_info` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/get-info.md
- `get_services` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/get-services.md
- `get_unfilled_request_template` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/get-unfilled-request-template.md
- `lookup_duplicate_referral_deadline` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/lookup-duplicate-referral-deadline.md
- `lookup_exit_route` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/lookup-exit-route.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-geezerkeeper-referral-exit-routes · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-geezerkeeper-referral-exit-routes