verify_charity
Look up a charity by its official registry identifier - EIN (US), Charity Commission number (GB), RSIN (NL), AHU/Kemenkumham reg number (ID), or a generic registration_number for other countries. Returns the matched charity or null. Use this when the user provides a registry number and wants to c...
This record as markdown: /tools/com-giveradar-charity-registry/verify-charity.md
What verify_charity does on Charity Registry
AI agents call verify_charity 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 |
|---|---|---|---|
country | string | Yes | ISO 3166-1 alpha-2 country code. |
id_value | string | Yes | The registration / EIN / charity number. |
Parameters from the server's own tool schema.
Why verify_charity is rated Low
This tool queries official government charity registries using identifiers (EIN, Charity Commission number, etc.) and retrieves matching records. It performs a lookup with no side effects, mutations, or irreversible actions. The return value is a matched charity record or null, confirming it is purely informational retrieval.
From the tool's definition Tool description states 'Look up a charity' and 'Returns the matched charity or null' — core read operation. No modification, deletion, or execution described.
Attacks that exploit this kind of access
The rule that runs verify_charity 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 verify_charity, this is the rule to start with:
verify_charity 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 verify_charity call is checked against it from then on.
Questions about verify_charity
Look up a charity by its official registry identifier - EIN (US), Charity Commission number (GB), RSIN (NL), AHU/Kemenkumham reg number (ID), or a generic registration_number for other countries. Returns the matched charity or null. Use this when the user provides a registry number and wants to confirm what's registered under it. It is categorised as a Read tool in the Charity Registry MCP Server, which means it retrieves data without modifying state.
verify_charity accepts 2 parameters: country, id_value. Required: country, id_value. 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 verify_charity: 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.
verify_charity 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 verify_charity 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 verify_charity. 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.
verify_charity 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