Explain why a specific market moved, using wallet flow, movers, feed, and arbitrage signals. Requires at least one of: marketId, conditionId, or query to identify the market. Returns a directional read and bottom-line interpretation.
AI agents call explain_market_move to retrieve information from Musashi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and synthesizes market intelligence data (wallet flow, movers, feed, arbitrage signals) to explain a market movement. It returns an analytical interpretation with no side effects, modifications, or financial transactions. Pure read/query operation.
From the tool's definition Explain why a specific market moved, using wallet flow, movers, feed, and arbitrage signals... Returns a directional read and bottom-line interpretation.
Attacks that exploit this kind of access
Explain why a specific market moved, using wallet flow, movers, feed, and arbitrage signals. Requires at least one of: marketId, conditionId, or query to identify the market. Returns a directional read and bottom-line interpretation. It is categorised as a Read tool in the Musashi MCP Server, which means it retrieves data without modifying state.
Register the Musashi MCP server in PolicyLayer and add a rule for explain_market_move: 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 Musashi. Nothing to install.
explain_market_move 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 explain_market_move 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 explain_market_move. 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.
explain_market_move is provided by the Musashi MCP server (musashibot/musashi-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 →