CRITICAL: Check a token
AI agents call check_token_risk 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 retrieves or analyzes existing data about a token's risk profile. It has no side effects—it does not execute transactions, modify blockchain state, move funds, or delete data. The 'CRITICAL' emphasis in the description refers to the importance of the information for decision-making, not the severity of the tool's actions.
From the tool's definition Tool name 'check_token_risk' and description 'Check a token' indicate a query/lookup operation. The server context confirms it retrieves risk intelligence data (rug pulls, honeypots, scams) to inform decisions, but performs no state changes, fund movements,…
Attacks that exploit this kind of access
CRITICAL: Check a token. 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 check_token_risk: 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.
check_token_risk 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 check_token_risk 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 check_token_risk. 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.
check_token_risk 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 →