Search OPEN PHILANTHROPY JOBS at grantmaking foundations. Surfaces roles involved in giving away money, running philanthropic programs, or executive leadership of philanthropic work. Backed by a weekly scrape of ~50K funder careers pages + GPT-5.4-mini classification against an 8-category taxonom...
Risk signalsAccepts freeform code/query input (query) · High parameter count (12 properties)
Part of the Foundation Discovery server.
Free to start. No card required.
AI agents call search_funder_jobs 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 search_funder_jobs 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.
{
"version": "1",
"default": "deny",
"tools": {
"search_funder_jobs": {}
}
}See the full Foundation Discovery policy for all 10 tools.
These attack patterns abuse exactly the kind of access search_funder_jobs gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search OPEN PHILANTHROPY JOBS at grantmaking foundations. Surfaces roles involved in giving away money, running philanthropic programs, or executive leadership of philanthropic work. Backed by a weekly scrape of ~50K funder careers pages + GPT-5.4-mini classification against an 8-category taxonomy. Categories (use the category param to filter): - grantmaking: Program officers, grants managers, RFP reviewers - program_leadership: VP Programs, Chief Program Officer, Program Director (cause-area) - executive_leadership: CEO, President, Executive Director at a foundation or community foundation - philanthropy_operations: Foundation finance/HR/IT/COO - program_support: Program associates, M&E officers, learning officers, program coordinators - development_for_grantmaking: Major gifts officers and development roles at community foundations and other regranting entities (NOT university or hospital development for the parent's operations) - philanthropy_communications: Foundation comms staff - philanthropy_strategy: Chief Strategy Officer, impact officer, equity & inclusion at a foundation What's excluded by design: clinical/medical, retail, academic teaching, university advancement for the university itself, hospital fundraising for hospital ops, construction/facilities. Args: query: Keyword search on job title (case-insensitive substring). Examples: "program officer", "grants manager", "CEO", "communications director". state: 2-letter US state code (e.g., "CA", "NY"). Uses a broad SQL prefilter plus an exact token-aware post-filter against the location field. country: Funder HQ country — ISO 3166-1 alpha-2 ("US", "GB", "DE") or a recognized name ("United Kingdom", "Germany"). Filters by where the FOUNDATION is headquartered; the corpus spans European funders, not just US. Independent of state (US foundations are the only ones with state-level location data). funder_ein: Restrict to one funder by EIN (9 digits, optional prefixes/dashes accepted). funder_eins: Restrict to a LIST of funder EINs (up to 100). The recommended compositional pattern is search_funders → search_funder_jobs(funder_eins=[...]) for cause-area searches (climate, racial equity, youth, etc.) where the cause isn't captured by the 8 role-family categories. category: One of the 8 philanthropy categories above. employment_type: full-time | part-time | contract | internship | fellowship | temporary. remote: remote | hybrid | on-site. posted_within_days: Recency window. Rows with NULL posted_at (common for HTML-scraped postings) are always kept. Default 365. limit: Max results (1-50). Default 20. Returns: Dictionary with results (list of jobs — title, funder_name, funder_ein, funder_kindora_url, location, remote_status, employment_type, philanthropy_category, posted_at, days_since_posted, apply_url, source), total_returned, summary (category_breakdown + remote_breakdown + posted_within_30_days), query_params, and note. Examples: search_funder_jobs(query="program officer") search_funder_jobs(category="grantmaking", state="NY") search_funder_jobs(category="executive_leadership", remote="remote") search_funder_jobs(country="GB") # UK-headquartered foundations search_funder_jobs(country="Germany", category="grantmaking") search_funder_jobs(funder_ein="131684331") # Ford Foundation only search_funder_jobs(employment_type="fellowship") search_funder_jobs() # Browse recent philanthropy jobs # Cause-area pattern (two-step composition): # Step 1: eins = search_funders(query="climate")["results"][:30].pluck("ein") # Step 2: search_funder_jobs(funder_eins=eins, category="grantmaking") Related tools: - search_funders: Find the grantmaking organizations themselves (use this FIRST for cause-area searches, then pass EINs to search_funder_jobs via funder_eins) - get_funder_profile: Detailed profile for one foundation - search_open_grants: Find open grant programs (not jobs). It is categorised as a Read tool in the Foundation Discovery MCP Server, which means it retrieves data without modifying state.
Register the Foundation Discovery MCP server in PolicyLayer and add a rule for search_funder_jobs: 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.
search_funder_jobs 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 search_funder_jobs 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 search_funder_jobs. 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.
search_funder_jobs 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.
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.