Check a token deployer
AI agents call check_deployer_history 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 information about token deployers to assess risk—a read-only operation with no side effects. It retrieves existing data rather than modifying, executing code, or deleting anything. The low severity reflects that misuse would only expose unwanted information, not cause irreversible harm or financial loss.
From the tool's definition Tool name 'check_deployer_history' and description 'Check a token deployer' indicate a lookup/query operation that retrieves historical information about a token deployer.
Attacks that exploit this kind of access
Check a token deployer. 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_deployer_history: 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_deployer_history 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_deployer_history 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_deployer_history. 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_deployer_history 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 →