Check if a token is community-flagged. Community-sourced intelligence
AI agents call check_blacklist 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 a read-only lookup against a community-maintained blacklist. It queries existing data to return risk intelligence but does not create, modify, delete, execute commands, or move funds. The severity is low because misuse would only return false information, not cause financial loss or irreversible damage.
From the tool's definition Tool name 'check_blacklist' and description 'Check if a token is community-flagged. Community-sourced intelligence' indicate a query operation that retrieves and reports pre-existing blacklist data without modifying any state.
Attacks that exploit this kind of access
Check if a token is community-flagged. Community-sourced intelligence. 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_blacklist: 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_blacklist 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_blacklist 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_blacklist. 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_blacklist 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 →