lookup_exit_route
Return a maintained stop-contact and privacy route for one supported senior-care referral network. Input is only a network identifier; never provide personal information.
This record as markdown: /tools/com-geezerkeeper-referral-exit-routes/lookup-exit-route.md
What lookup_exit_route does on GeezerKeeper Referral Exit Routes and Deadlines
AI agents call lookup_exit_route 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
sourceId | string | Yes | Referral network: apfm, caring, seniorly, or seniorhousingnet |
Parameters from the server's own tool schema.
Why lookup_exit_route is rated Low
This tool purely queries and retrieves static reference information about senior-care network exit routes based on a network identifier. It has no side effects, does not modify data, execute code, delete information, or handle financial transactions. The explicit constraints against providing PII and the read-only nature of the server confirm the Read category.
From the tool's definition Tool description explicitly states it 'Return[s] a maintained stop-contact and privacy route' with 'Input is only a network identifier; never provide personal information.' The server description confirms 'Read-only' access with 'no PII or sending.' The tool…
Attacks that exploit this kind of access
The rule that runs lookup_exit_route 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 lookup_exit_route, this is the rule to start with:
lookup_exit_route 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 lookup_exit_route call is checked against it from then on.
Questions about lookup_exit_route
Return a maintained stop-contact and privacy route for one supported senior-care referral network. Input is only a network identifier; never provide personal information. 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.
lookup_exit_route accepts 1 parameter: sourceId. Required: sourceId. The full parameter table on this page comes from the server's own tool schema.
Register the GeezerKeeper Referral Exit Routes and Deadlines MCP server in PolicyLayer and add a rule for lookup_exit_route: 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.
lookup_exit_route 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 lookup_exit_route 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 lookup_exit_route. 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.
lookup_exit_route 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