get_performance_history
AI agents call get_performance_history to retrieve information from Investment Statement MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical performance metrics from stored investment data without modifying, deleting, or executing external operations. The pattern across sibling tools (all get_* queries) and the server's design as a statement parser/query system strongly indicates read-only data retrieval.
From the tool's definition Tool name 'get_performance_history' indicates retrieval of historical performance data. Server context describes 'query investment statements' and 'semantic search for dividends, holdings, transactions, and account balances' as read-only operations.
Attacks that exploit this kind of access
get_performance_history. It is categorised as a Read tool in the Investment Statement MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Investment Statement MCP Server MCP server in PolicyLayer and add a rule for get_performance_history: 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 Investment Statement MCP Server. Nothing to install.
get_performance_history 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_performance_history 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_performance_history. 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_performance_history is provided by the Investment Statement MCP Server MCP server (vinnycarter05/investing-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 →