# choose_private_workflow

Choose the free, $19 consumer, or $59 professional option using only recipient count and intended use. No personal information is accepted.

Agent View of the PolicyLayer registry record for `choose_private_workflow`. HTML page: https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/choose-private-workflow

## Facts

- Tool: `choose_private_workflow`
- 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: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `recipientCount` | integer | yes | Number of identifiable organizations to track |
| `professionalUse` | boolean | no | 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.

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

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

## 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.

## Use case

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.

## 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": {
    "choose_private_workflow": {}
  }
}
```

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

- `get_info` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/get-info.md
- `get_location` — Read — https://policylayer.com/tools/com-geezerkeeper-referral-exit-routes/get-location.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