nonprofit_search_name
Fuzzy-search tax-exempt organizations by name, optionally filtered to a US state. Tolerant of word reordering and minor spelling differences. Returns ranked matches with EIN, location, and IRC subsection. Use the returned EIN with nonprofit_details or nonprofit_lookup_ein.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nonprofit-search-name.md
What nonprofit_search_name does on Livedatalink
AI agents call nonprofit_search_name 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 |
|---|---|---|---|
name | string | Yes | Organization name or partial name to search for. |
limit | number | — | Max matches to return (default 10, max 50). |
state | string | — | Optional 2-letter US state/territory code to narrow results, e.g. "NY", "TX", "CA". |
Parameters from the server's own tool schema.
Why nonprofit_search_name is rated Low
This tool queries a public database of tax-exempt organizations and returns search results. It has no side effects, does not modify data, does not execute code or commands, and does not involve financial transactions. It is purely informational retrieval. The low severity reflects that misuse would only expose public nonprofit information already available through IRS databases.
From the tool's definition Tool performs 'Fuzzy-search' and 'Returns ranked matches' on tax-exempt organization data; described as a search operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs nonprofit_search_name 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_name, this is the rule to start with:
nonprofit_search_name 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_name call is checked against it from then on.
Questions about nonprofit_search_name
Fuzzy-search tax-exempt organizations by name, optionally filtered to a US state. Tolerant of word reordering and minor spelling differences. Returns ranked matches with EIN, location, and IRC subsection. Use the returned EIN with nonprofit_details or nonprofit_lookup_ein. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
nonprofit_search_name accepts 3 parameters: name, limit, state. Required: name. 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_name: 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_name 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_name 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_name. 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_name 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