Query historical data for US stocks. Supports fuzzy search by name (e.g.
AI agents call query_us_stock_data to retrieve information from Stock Data 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 and supports fuzzy search—purely informational operations with no side effects. It does not execute trades, modify data, delete records, or commit financial obligations. While the server provides 'trading suggestions', this specific tool only queries data, making it a Read operation with low risk.
From the tool's definition Tool name 'query_us_stock_data' and description 'Query historical data for US stocks' indicate retrieval of market data with no modification capability.
Attacks that exploit this kind of access
Query historical data for US stocks. Supports fuzzy search by name (e.g. It is categorised as a Read tool in the Stock Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stock Data MCP Server MCP server in PolicyLayer and add a rule for query_us_stock_data: 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 Data MCP Server. Nothing to install.
query_us_stock_data 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 query_us_stock_data 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 query_us_stock_data. 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.
query_us_stock_data is provided by the Stock Data MCP Server MCP server (xj-bear/stockdata-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 →