Return a list of available crypto-related stocks in a table format.
AI agents call get_stock_list to retrieve information from Crypto Stocks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries available stocks, which is a pure Read operation. No data is created, modified, deleted, or executed. The blast radius is minimal—misuse simply returns a list of stocks. Severity is low because the information returned is likely public market data with no financial or destructive consequences.
From the tool's definition Tool name 'get_stock_list' and description 'Return a list of available crypto-related stocks in a table format' indicate a retrieval operation with no side effects. Returns data without modification or execution.
Attacks that exploit this kind of access
Return a list of available crypto-related stocks in a table format. It is categorised as a Read tool in the Crypto Stocks MCP Server, which means it retrieves data without modifying state.
Register the Crypto Stocks MCP server in PolicyLayer and add a rule for get_stock_list: 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 Crypto Stocks. Nothing to install.
get_stock_list 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_list 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_list. 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_list is provided by the Crypto Stocks MCP server (kukapay/crypto-stocks-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 →