search_stocks
AI agents call search_stocks to retrieve information from yfinance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve and query data without modification, deletion, or execution of external operations. Even though the description is empty, the tool name and the pattern of sibling tools—all read-only financial data retrievals—strongly indicate this is a Read operation. Low severity because querying stock data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'search_stocks' and sibling tools on this server (get_analyst_estimates, get_analyst_ratings, get_dividends, get_earnings, get_financials, get_historical_data, get_insider_holdings, get_esg_data) all perform data retrieval operations from Yahoo…
Attacks that exploit this kind of access
search_stocks. It is categorised as a Read tool in the yfinance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the yfinance MCP Server MCP server in PolicyLayer and add a rule for search_stocks: 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 yfinance MCP Server. Nothing to install.
search_stocks 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 search_stocks 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 search_stocks. 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.
search_stocks is provided by the yfinance MCP Server MCP server (torosent/yfinance-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 →