AI agents call get_stock_history to retrieve information from Stock-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical price data for stocks. It performs a read-only operation on market data with no side effects—no creation, modification, deletion, or execution of code/commands. The 80-day historical data window is fixed and the tool only retrieves existing information. Severity is low because misuse would only expose historical market data already publicly available through financial sources.
From the tool's definition Tool name 'get_stock_history' and description '获取个股80天历史行情数据' (retrieve individual stock 80-day historical price data) indicate pure data retrieval with no modification, deletion, or external execution.
Attacks that exploit this kind of access
获取个股80天历史行情数据. It is categorised as a Read tool in the Stock-MCP MCP Server, which means it retrieves data without modifying state.
Register the Stock- 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-MCP. 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- MCP server (nomi982/stock-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 →