nonprofit_status
Current exempt-organization status for one organization by EIN: whether the IRS recognition is active, revoked, or terminated, plus the decoded status label, contribution deductibility, and the ruling (recognition) date. Tells donors and grantmakers if an org is still in good standing.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nonprofit-status.md
What nonprofit_status does on Livedatalink
AI agents call nonprofit_status 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 |
|---|---|---|---|
ein | string | Yes | Employer Identification Number (EIN). Accepts 9 digits with or without a dash, e.g. "13-1837418" or "131837418". |
Parameters from the server's own tool schema.
Why nonprofit_status is rated Low
This tool retrieves publicly available IRS nonprofit status information and performs no side effects. No data is created, modified, deleted, or executed. The output informs decisions but does not change any systems or records. It falls squarely in the Read category (retrieve/query with no side effects).
From the tool's definition Tool queries and retrieves current nonprofit status data by EIN, returning fields like exempt status, deductibility, and ruling date.
Attacks that exploit this kind of access
The rule that runs nonprofit_status 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_status, this is the rule to start with:
nonprofit_status 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_status call is checked against it from then on.
Questions about nonprofit_status
Current exempt-organization status for one organization by EIN: whether the IRS recognition is active, revoked, or terminated, plus the decoded status label, contribution deductibility, and the ruling (recognition) date. Tells donors and grantmakers if an org is still in good standing. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
nonprofit_status accepts 1 parameter: ein. Required: ein. 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_status: 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_status 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_status 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_status. 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_status 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