Get market data for a coin
AI agents call get_market_data to retrieve information from Multi-MCPs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves cryptocurrency market data (price, volume, etc.) for a specified coin. It performs a query operation with no side effects, data modification, code execution, or financial transaction. The low severity reflects that querying public market data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_market_data' and description 'Get market data for a coin' indicate data retrieval without modification. The verb 'Get' and absence of any mutation language confirm read-only operation.
Attacks that exploit this kind of access
Get market data for a coin. It is categorised as a Read tool in the Multi-MCPs MCP Server, which means it retrieves data without modifying state.
Register the Multi-MCPs MCP server in PolicyLayer and add a rule for get_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 Multi-MCPs. Nothing to install.
get_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 get_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 get_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.
get_market_data is provided by the Multi-MCPs MCP server (taylorchen/muti-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_market_data is one line of Multi-MCPs's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →