ftg_investor_directory
Return investors from the FTG directory — VC, PE and impact funds with type, firm, website, ticket-size range, sectors and stages of interest. When to use this tool: an agent builds a fundraising shortlist. Input: optional country and limit.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/ftg-investor-directory.md
What ftg_investor_directory does on Mcp Knowledge
AI agents call ftg_investor_directory to retrieve information from Mcp Knowledge 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 |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
limit | integer | — | |
country | string | — | Optional country ISO code or name |
Parameters from the server's own tool schema.
Why ftg_investor_directory is rated Low
The tool only retrieves and returns directory data about investors. It has no side effects, makes no financial commitments, and does not modify any data. It is a straightforward lookup/query operation with minimal blast radius if misused.
From the tool's definition Return investors from the FTG directory — VC, PE and impact funds with type, firm, website, ticket-size range, sectors and stages of interest
Attacks that exploit this kind of access
The rule that runs ftg_investor_directory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ftg_investor_directory, this is the rule to start with:
ftg_investor_directory 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 Mcp Knowledge, apply this rule, and every ftg_investor_directory call is checked against it from then on.
Questions about ftg_investor_directory
Return investors from the FTG directory — VC, PE and impact funds with type, firm, website, ticket-size range, sectors and stages of interest. When to use this tool: an agent builds a fundraising shortlist. Input: optional country and limit. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
ftg_investor_directory accepts 3 parameters: async, limit, country. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for ftg_investor_directory: 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 Mcp Knowledge. Nothing to install.
ftg_investor_directory 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 ftg_investor_directory 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 ftg_investor_directory. 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.
ftg_investor_directory is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue