AI agents call get_investment_transactions_tool to retrieve information from Plaid 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 brokerage transaction data without modifying it. However, severity is high rather than low because access to detailed investment transaction history reveals sensitive financial information including trading patterns, portfolio composition, and financial behavior—information valuable for targeted attacks, fraud, or unauthorized disclosure.
From the tool's definition Tool name includes 'get_' indicating retrieval; description states 'Brokerage transactions: buys, sells, dividends, fees' which enumerates historical transaction data.
Attacks that exploit this kind of access
Brokerage transactions: buys, sells, dividends, fees. It is categorised as a Read tool in the Plaid MCP Server, which means it retrieves data without modifying state.
Register the Plaid MCP server in PolicyLayer and add a rule for get_investment_transactions_tool: 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 Plaid. Nothing to install.
get_investment_transactions_tool 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_investment_transactions_tool 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_investment_transactions_tool. 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_investment_transactions_tool is provided by the Plaid MCP server (t-rhex/plaid-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 →