fundos_list_transactions
Use this to view term sheets and closings in flight when reporting on closing pipeline or chasing CPs. Optional status filter (drafting|negotiating|signed|funding|closed|cancelled). Returns Transaction objects.
This record as markdown: /tools/8vdx1-fundos-mcp/fundos-list-transactions.md
What fundos_list_transactions does on Fundos
AI agents call fundos_list_transactions to retrieve information from Fundos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fundos_list_transactions is rated Low
This tool retrieves and queries fund transaction data (term sheets, closings) filtered by status. It has no side effects—it does not modify, delete, or execute operations. The use case ('reporting on closing pipeline or chasing CPs') confirms read-only information gathering.
From the tool's definition Tool description states 'view term sheets and closings' and 'Returns Transaction objects' with optional filtering. The verb 'list' and 'view' indicate retrieval without modification.
Attacks that exploit this kind of access
The rule that runs fundos_list_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fundos_list_transactions, this is the rule to start with:
fundos_list_transactions 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 Fundos, apply this rule, and every fundos_list_transactions call is checked against it from then on.
Questions about fundos_list_transactions
Use this to view term sheets and closings in flight when reporting on closing pipeline or chasing CPs. Optional status filter (drafting|negotiating|signed|funding|closed|cancelled). Returns Transaction objects. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos MCP server in PolicyLayer and add a rule for fundos_list_transactions: 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 Fundos. Nothing to install.
fundos_list_transactions 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 fundos_list_transactions 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 fundos_list_transactions. 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.
fundos_list_transactions is provided by the Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
This server
Across the catalogue