AI agents call fetch_market_data to retrieve information from Ai Trader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries market data without creating, modifying, or deleting anything. It has no side effects and represents a standard read operation. The empty description slightly reduces confidence, but the tool name and server context make the classification clear.
From the tool's definition Tool name 'fetch_market_data' indicates retrieval of market data with no modification. Server description confirms it 'fetch[es] market data' as a read operation.
Attacks that exploit this kind of access
fetch_market_data. It is categorised as a Read tool in the Ai Trader MCP Server, which means it retrieves data without modifying state.
Register the Ai Trader MCP server in PolicyLayer and add a rule for fetch_market_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 Ai Trader. Nothing to install.
fetch_market_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_market_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_market_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_market_data is provided by the Ai Trader MCP server (whchien/ai-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.