AI agents call get_movers 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.
This tool queries market intelligence to surface price movement information. It has no side effects, does not execute trades, does not modify data, and does not trigger financial transactions. It is purely informational retrieval, fitting the 'Read' category. The low severity reflects that misuse by an AI agent would result in gathering market information only, with no ability to affect markets or accounts.
From the tool's definition Tool description: 'Get markets with the biggest recent price moves' — retrieves market data without modification or execution of transactions. The verb 'Get' and read-only nature (queries historical/current price movements) indicates data retrieval.
Attacks that exploit this kind of access
Get markets with the biggest recent price moves. Use this when the user asks what is moving, what changed, or wants to see large price swings. 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 get_movers: 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.
get_movers 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_movers 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_movers. 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_movers 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 →