org_funding_profile
One-call federal-money + nonprofit profile for an organization: USAspending contracts and grants recipient summaries (total dollars, award counts, top agencies), IRS 990 exempt-organization details (revenue/assets/income, NTEE, subsection, exempt status) by EIN or name+state, and optionally open ...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/org-funding-profile.md
What org_funding_profile does on Livedatalink
AI agents call org_funding_profile 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 | — | Optional EIN for an exact IRS 990 match. |
state | string | — | Optional 2-letter state to disambiguate a nonprofit name search. |
organization | string | Yes | Organization / company / nonprofit name. |
include_opportunities | boolean | — | Also list open Grants.gov funding opportunities (available, not awarded). Default false. |
Parameters from the server's own tool schema.
Why org_funding_profile is rated Low
Even though org_funding_profile only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs org_funding_profile 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 org_funding_profile, this is the rule to start with:
org_funding_profile 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 org_funding_profile call is checked against it from then on.
Questions about org_funding_profile
One-call federal-money + nonprofit profile for an organization: USAspending contracts and grants recipient summaries (total dollars, award counts, top agencies), IRS 990 exempt-organization details (revenue/assets/income, NTEE, subsection, exempt status) by EIN or name+state, and optionally open Grants.gov OPPORTUNITIES (clearly labeled as available funding to apply for, NOT awards received). Sources degrade gracefully. Premium cross-source synthesis; federal dollars are name-matched and should be verified. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
org_funding_profile accepts 4 parameters: ein, state, organization, include_opportunities. Required: organization. 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 org_funding_profile: 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.
org_funding_profile 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 org_funding_profile 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 org_funding_profile. 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.
org_funding_profile 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