Get portfolio history.
AI agents call get_portfolio_history to retrieve information from Corpus 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 portfolio data without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk if misused by an AI agent—the worst outcome is accessing sensitive financial information the agent may not be authorized to view, but no data is altered or transactions are executed. Classification as Read is appropriate.
From the tool's definition Tool name 'get_portfolio_history' and description 'Get portfolio history' indicate a retrieval operation with no modification or side effects. The verb 'Get' and the context of a financial tracking system confirm this is a query-only function.
Attacks that exploit this kind of access
Get portfolio history. It is categorised as a Read tool in the Corpus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Corpus MCP Server MCP server in PolicyLayer and add a rule for get_portfolio_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 Corpus MCP Server. Nothing to install.
get_portfolio_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_portfolio_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_portfolio_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_portfolio_history is provided by the Corpus MCP Server MCP server (mathankarthik18/corpus-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 →