Low Risk

get_funder_profile

Get detailed profile information for a specific funder. Polymorphic identifier — pass ein for US 990 foundations OR funder_id (bare UUID / n9f:<uuid>) for non-990 funders such as European, UK 360Giving, and Canadian CRA T3010 funders. search_funders returns both fields on every hit, so the caller...

Part of the Foundation Discovery server.

get_funder_profile is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE FOUNDATION DISCOVERY →

Free to start. No card required.

AI agents call get_funder_profile to retrieve information from Foundation Discovery without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_funder_profile only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_funder_profile": {}
  }
}

See the full Foundation Discovery policy for all 10 tools.

Get this rule live on your own Foundation Discovery server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FOUNDATION DISCOVERY →

View all 10 tools →

These attack patterns abuse exactly the kind of access get_funder_profile gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_funder_profile only ever does what you allow.

SECURE FOUNDATION DISCOVERY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_funder_profile tool do? +

Get detailed profile information for a specific funder. Polymorphic identifier — pass ein for US 990 foundations OR funder_id (bare UUID / n9f:<uuid>) for non-990 funders such as European, UK 360Giving, and Canadian CRA T3010 funders. search_funders returns both fields on every hit, so the caller can hand either one back here. At least one identifier must be supplied. Use this after searching for funders to get detailed information about a specific one. Args: ein: Foundation EIN (9 digits) for US 990 funders. Can include hyphens (e.g., "94-3136777") or be provided as digits only (e.g., "943136777"). Optional if funder_id is supplied for a non-990 funder. funder_id: Optional non-990 funder id. Accepts a bare UUID or n9f:<uuid> / non990:<uuid>. The usf:<ein> prefix is also accepted and routes back to the EIN path. Returns: Dictionary containing: - ein: The normalized 9-digit EIN (US 990 path) or empty string (non-990 path) - funder_id: The UUID (non-990 path only) - profile: Funder profile data — legal_name, location, financials (with currency for non-990 funders; amounts NEVER converted), contact, classification. For non-990 sources the profile also surfaces mission_statement / generated_summary / industry_alignment_tags / data_provenance.source_label when enrichment has been run (sparse on freshly-ingested CRA T3010 rows; populated for European seeds). - note: Suggestions for related tools to explore Examples: get_funder_profile(ein="943136777") get_funder_profile(funder_id="n9f:60ef21da-dc33-4b9f-82b3-f22a5d433623") Related tools: - search_funders: Find funder ids by name or location - get_990_summary: 990 financial trends (US 990 only) - get_foundation_grants: Grant history (works for both paths) - get_funder_stats: Aggregate giving statistics (works for both paths). It is categorised as a Read tool in the Foundation Discovery MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_funder_profile? +

Register the Foundation Discovery MCP server in PolicyLayer and add a rule for get_funder_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 Foundation Discovery. Nothing to install.

What risk level is get_funder_profile? +

get_funder_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_funder_profile? +

Yes. Add a rate_limit block to the get_funder_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.

How do I block get_funder_profile completely? +

Set action: deny in the PolicyLayer policy for get_funder_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.

What MCP server provides get_funder_profile? +

get_funder_profile is provided by the Foundation Discovery MCP server (https://kindora-mcp.azurewebsites.net/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Foundation Discovery tool call.

Deterministic rules across all 10 Foundation Discovery tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.