diagnose_stock
AI agents call diagnose_stock to retrieve information from Stock MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or analyze stock diagnostic information rather than modify, execute, or destroy data. The empty description lowers confidence slightly, but the consistent pattern of sibling tools being read-only analyses and the 'diagnose' naming (suggesting inspection/analysis rather than action) indicates this is a Read operation. Severity is low as it retrieves financial data without side effects.
From the tool's definition Tool named 'diagnose_stock' on a stock analysis server with sibling tools that are all Read operations (get_stock_analysis, search_stock, screen_kr_breakout, etc.). No description provided, but the naming convention and server context indicate data retrieval.
Attacks that exploit this kind of access
diagnose_stock. It is categorised as a Read tool in the Stock MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stock MCP Server MCP server in PolicyLayer and add a rule for diagnose_stock: 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 Server. Nothing to install.
diagnose_stock 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 diagnose_stock 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 diagnose_stock. 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.
diagnose_stock is provided by the Stock MCP Server MCP server (juuuuuuni/stock-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 →