AI agents call get_project_fund_transactions to retrieve information from Filevine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing trust/retainer fund transaction history. It performs a read-only lookup operation with no side effects—it neither executes financial transactions, modifies data, nor triggers external operations. While it accesses financial information (which could be sensitive), the action itself is purely informational retrieval.
From the tool's definition Tool name 'get_project_fund_transactions' and description 'Get trust/retainer fund transaction history for a project' indicate retrieval of historical financial data with no modification or execution of transactions.
Attacks that exploit this kind of access
Get trust/retainer fund transaction history for a project. It is categorised as a Read tool in the Filevine MCP Server, which means it retrieves data without modifying state.
Register the Filevine MCP server in PolicyLayer and add a rule for get_project_fund_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 Filevine. Nothing to install.
get_project_fund_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 get_project_fund_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 get_project_fund_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.
get_project_fund_transactions is provided by the Filevine MCP server (rosenadvertising/filevine-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 →