compare_charities
Side-by-side comparison of 2-5 charities by slug. Returns their integrity scores, program/admin/fundraising ratios, annual revenue, founding year, foundation type, and a deterministic verdict on which has the strongest transparency signal. Use this when the user wants to choose between named char...
This record as markdown: /tools/com-giveradar-charity-registry/compare-charities.md
What compare_charities does on Charity Registry
AI agents call compare_charities to retrieve information from Charity Registry 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 |
|---|---|---|---|
slugs | array | Yes | Charity slugs to compare (2-5). |
Parameters from the server's own tool schema.
Why compare_charities is rated Low
This tool retrieves and presents comparative information about charities from a read-only registry. It queries existing data and synthesizes it for user comparison, with no capability to modify, delete, or execute external actions. The deterministic verdict is analytical output, not a state-changing operation.
From the tool's definition Tool description specifies 'side-by-side comparison' and 'returns' data (integrity scores, ratios, revenue, founding year, foundation type, transparency signal). No mutations, deletions, or external operations are performed.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs compare_charities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Charity Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_charities, this is the rule to start with:
compare_charities 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 Charity Registry, apply this rule, and every compare_charities call is checked against it from then on.
Questions about compare_charities
Side-by-side comparison of 2-5 charities by slug. Returns their integrity scores, program/admin/fundraising ratios, annual revenue, founding year, foundation type, and a deterministic verdict on which has the strongest transparency signal. Use this when the user wants to choose between named charities. It is categorised as a Read tool in the Charity Registry MCP Server, which means it retrieves data without modifying state.
compare_charities accepts 1 parameter: slugs. Required: slugs. The full parameter table on this page comes from the server's own tool schema.
Register the Charity Registry MCP server in PolicyLayer and add a rule for compare_charities: 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 Charity Registry. Nothing to install.
compare_charities 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 compare_charities 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 compare_charities. 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.
compare_charities is provided by the Charity Registry MCP server (https://giveradar.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Charity Registry, and thousands of servers like it.
This server
Across the catalogue