AI agents call fetch_stock_data to retrieve information from StocksMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial data without side effects. It queries and returns information (fundamentals, quarterly results, historical prices) but does not create, modify, delete, execute code, or commit financial transactions. The highest risk would be if confidential data were exposed, but the description suggests public market data. Classified as Read with low severity.
From the tool's definition Tool name contains 'fetch' and description states 'Fetch the latest fundamentals, quarterly financial results, and historical price data' — all read-only retrieval operations with no modification or deletion of data.
Attacks that exploit this kind of access
Fetch the latest fundamentals, quarterly financial results, and historical price data. It is categorised as a Read tool in the StocksMCP MCP Server, which means it retrieves data without modifying state.
Register the Stocks MCP server in PolicyLayer and add a rule for fetch_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 StocksMCP. Nothing to install.
fetch_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 fetch_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 fetch_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.
fetch_stock_data is provided by the Stocks MCP server (pawanthanay/stocksmcp). 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 →