AI agents call get_smart_money_markets 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 and returns market data filtered by smart-wallet activity patterns. It is a passive read operation that retrieves information for analysis without modifying data, executing external code, or moving funds. Consistent with sibling tools like 'get_movers', 'get_market_brief', and 'get_feed' which are all informational queries.
From the tool's definition Tool name 'get_smart_money_markets' and description 'Find markets with unusual smart-wallet activity' indicate data retrieval and analysis of existing market intelligence. No mutation, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
Find markets with unusual smart-wallet activity. 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_smart_money_markets: 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_smart_money_markets 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_smart_money_markets 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_smart_money_markets. 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_smart_money_markets 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 →