Retrieve historical data for a stock given a ticker symbol and a period.
AI agents call get_stock_history to retrieve information from Stock Assistant 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 stock data via the Yahoo Finance API based on input parameters (ticker symbol and period). The verb 'retrieve' and the read-only nature of querying historical financial data confirm this is a Read category tool.
From the tool's definition Tool name 'get_stock_history' and description 'Retrieve historical data for a stock' indicate a read-only operation that queries and returns data without modifying or executing any actions.
Attacks that exploit this kind of access
Retrieve historical data for a stock given a ticker symbol and a period. It is categorised as a Read tool in the Stock Assistant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stock Assistant MCP Server MCP server in PolicyLayer and add a rule for get_stock_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 Stock Assistant MCP Server. Nothing to install.
get_stock_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_stock_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_stock_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_stock_history is provided by the Stock Assistant MCP Server MCP server (shwetha-sundar/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 →