get_price_history
AI agents call get_price_history to retrieve information from Financial MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve historical price data for financial analysis purposes. While the empty description reduces confidence slightly, the tool name and context of sibling read-only tools (get_portfolio, get_company_overview, get_stock_quote) strongly suggest this is a data retrieval operation with no side effects.
From the tool's definition Tool name 'get_price_history' indicates data retrieval operation. Description is empty, but naming convention and sibling tools (get_stock_quote, get_stock_news, market_summary) all retrieve financial data without modification.
Attacks that exploit this kind of access
get_price_history. It is categorised as a Read tool in the Financial MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Financial MCP Server MCP server in PolicyLayer and add a rule for get_price_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 Financial MCP Server. Nothing to install.
get_price_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_price_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_price_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_price_history is provided by the Financial MCP Server MCP server (osamadev/financial_mcp_server). 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 →