X/Twitter-thread-ready forensic analysis. 5-8 posts, each ≤280 chars.
AI agents call marcus_thread 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 performs analysis composition and presentation of crypto token risk intelligence (already detected via sibling tools like check_token_risk). It formats and outputs findings in a specific medium (Twitter thread format) without modifying underlying data, executing external operations, or triggering financial transactions. The action is read-like: converting analyzed data into a presentation format.
From the tool's definition Tool generates forensic analysis formatted for Twitter/X threads with character limits (≤280 chars per post).
Attacks that exploit this kind of access
X/Twitter-thread-ready forensic analysis. 5-8 posts, each ≤280 chars. 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 marcus_thread: 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.
marcus_thread 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 marcus_thread 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 marcus_thread. 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.
marcus_thread 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 →