Deep holder analysis: sniper detection, Jito bundle analysis,
AI agents call get_holder_deepdive to retrieve information from Rug Munch Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and analyzes holder information, detects patterns (sniper detection, bundle analysis), and returns intelligence insights. There is no indication of state mutation, code execution, deletion, or financial transaction initiation. It is purely informational/analytical in nature, making it a Read operation with low severity risk.
From the tool's definition Tool name 'get_holder_deepdive' and description indicate data retrieval and analysis operations: 'Deep holder analysis: sniper detection, Jito bundle analysis' — these are investigative/analytical queries that examine blockchain data without modifying state.
Attacks that exploit this kind of access
Deep holder analysis: sniper detection, Jito bundle analysis,. It is categorised as a Read tool in the Rug Munch Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Rug Munch Intelligence MCP server in PolicyLayer and add a rule for get_holder_deepdive: 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 Rug Munch Intelligence. Nothing to install.
get_holder_deepdive 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_holder_deepdive 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_holder_deepdive. 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_holder_deepdive is provided by the Rug Munch Intelligence MCP server (marcus-rug-intel/rug-munch-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 →