search_funders
AI agents call search_funders to retrieve information from Kindora-for-ChatGPT MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query on publicly available funder data. No modification, deletion, or execution of arbitrary code occurs. The blast radius of misuse is minimal—an agent could retrieve information about funders, but cannot alter data, execute operations, or cause financial harm. Classified as Read with low severity.
From the tool's definition Tool name 'search_funders' indicates a search/query operation. Server context shows this is part of a grant discovery platform that 're-exposes Kindora's public funder and grant tools,' with sibling tools including 'get_foundation_grants',…
Attacks that exploit this kind of access
search_funders. It is categorised as a Read tool in the Kindora-for-ChatGPT MCP server MCP Server, which means it retrieves data without modifying state.
Register the Kindora-for-ChatGPT MCP server MCP server in PolicyLayer and add a rule for search_funders: 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 Kindora-for-ChatGPT MCP server. Nothing to install.
search_funders 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_funders 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_funders. 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_funders is provided by the Kindora-for-ChatGPT MCP server MCP server (wayanvota/kindora-chatgpt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →