get_info
Return canonical public business identity, contact, pricing range, and privacy-boundary information (PUBLICMCP v0.3). Accepts no inputs.
This record as markdown: /tools/com-geezerkeeper-referral-exit-routes/get-info.md
What get_info does on GeezerKeeper Referral Exit Routes and Deadlines
AI agents call get_info 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_info is rated Low
This is a read-only data retrieval operation that queries publicly available business information. No modifications, deletions, code execution, or financial transactions occur. The tool accepts no inputs, eliminating risk of argument injection. The server context confirms 'no PII or sending', further constraining scope to safe informational retrieval.
From the tool's definition Tool returns canonical public business identity, contact, pricing range, and privacy-boundary information with no input parameters. Description explicitly labels this as 'public' data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_info 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_info, this is the rule to start with:
get_info 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_info call is checked against it from then on.
Questions about get_info
Return canonical public business identity, contact, pricing range, and privacy-boundary information (PUBLICMCP v0.3). Accepts no inputs. 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_info: 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_info 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_info 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_info. 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_info 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