choose_private_workflow
Choose the free, $19 consumer, or $59 professional option using only recipient count and intended use. No personal information is accepted.
This record as markdown: /tools/com-geezerkeeper-referral-exit-routes/choose-private-workflow.md
What choose_private_workflow does on GeezerKeeper Referral Exit Routes and Deadlines
AI agents call choose_private_workflow 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 |
|---|---|---|---|
recipientCount | integer | Yes | Number of identifiable organizations to track |
professionalUse | boolean | — | True for a practice, firm, or senior living location sharing handouts or tracking referral chronology and deadlines |
Parameters from the server's own tool schema.
Why choose_private_workflow is rated Low
Even though choose_private_workflow only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs choose_private_workflow 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 choose_private_workflow, this is the rule to start with:
choose_private_workflow 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 choose_private_workflow call is checked against it from then on.
Questions about choose_private_workflow
Choose the free, $19 consumer, or $59 professional option using only recipient count and intended use. No personal information is accepted. 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.
choose_private_workflow accepts 2 parameters: recipientCount, professionalUse. Required: recipientCount. 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 choose_private_workflow: 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.
choose_private_workflow 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 choose_private_workflow 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 choose_private_workflow. 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.
choose_private_workflow 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