Batch risk check for up to 20 tokens at once.
AI agents call check_batch_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 and analyzes risk data about cryptocurrency tokens in batch. It performs no write operations, does not execute transactions, move funds, or delete data. The function is purely informational—it checks and reports risk metrics to help users make informed decisions before transacting. No side effects or irreversible changes occur from using this tool.
From the tool's definition Tool name 'check_batch_risk' and description 'Batch risk check for up to 20 tokens at once' indicate a query/retrieval operation that analyzes token risk intelligence without modifying state or executing transactions.
Attacks that exploit this kind of access
Batch risk check for up to 20 tokens at once. 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_batch_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_batch_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_batch_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_batch_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_batch_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 →