nonprofit_search_location
Find tax-exempt organizations by location: city, state, and/or 5-digit ZIP. At least one filter is required. Useful for discovering charities, churches, and foundations in an area. Returns up to 100 organizations.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nonprofit-search-location.md
What nonprofit_search_location does on Livedatalink
AI agents call nonprofit_search_location to retrieve information from Livedatalink 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 |
|---|---|---|---|
zip | string | — | 5-digit ZIP code. |
city | string | — | City name (combine with state for best results). |
limit | number | — | Max results to return (default 20, max 100). |
state | string | — | 2-letter US state/territory code, e.g. "TX". |
Parameters from the server's own tool schema.
Why nonprofit_search_location is rated Low
This tool performs a read-only query of publicly available nonprofit organization data filtered by location. There are no side effects, data modifications, code execution, deletions, or financial transactions. The data returned (tax-exempt organization information) is public information.
From the tool's definition Tool name contains 'search'; description states 'Find tax-exempt organizations' and 'Returns up to 100 organizations'. Action is querying/retrieving publicly available tax-exempt organization data by location filters (city, state, ZIP).
Attacks that exploit this kind of access
The rule that runs nonprofit_search_location safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nonprofit_search_location, this is the rule to start with:
nonprofit_search_location 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 Livedatalink, apply this rule, and every nonprofit_search_location call is checked against it from then on.
Questions about nonprofit_search_location
Find tax-exempt organizations by location: city, state, and/or 5-digit ZIP. At least one filter is required. Useful for discovering charities, churches, and foundations in an area. Returns up to 100 organizations. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
nonprofit_search_location accepts 4 parameters: zip, city, limit, state. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for nonprofit_search_location: 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 Livedatalink. Nothing to install.
nonprofit_search_location 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 nonprofit_search_location 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 nonprofit_search_location. 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.
nonprofit_search_location is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue