Scan any token contract for honeypot, rug pull, and security risks
AI agents call token_security to retrieve information from AgentPay x402 — Economic-intelligence layer for AI Agents 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 security information about token contracts. It does not execute code on the contract, does not modify blockchain state, does not transfer funds, and does not delete data. While it may inform financial decisions by agents, the tool itself only reads and reports findings.
From the tool's definition Tool performs 'scan' and detection of security risks on token contracts. The verb "scan" and the listed outputs (honeypot detection, rug pull identification, security risk assessment) indicate passive analysis of existing contract data with no modification,…
Attacks that exploit this kind of access
Scan any token contract for honeypot, rug pull, and security risks. It is categorised as a Read tool in the AgentPay x402 — Economic-intelligence layer for AI Agents MCP Server, which means it retrieves data without modifying state.
Register the AgentPay x402 — Economic-intelligence layer for AI Agents MCP server in PolicyLayer and add a rule for token_security: 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 AgentPay x402 — Economic-intelligence layer for AI Agents. Nothing to install.
token_security 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 token_security 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 token_security. 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.
token_security is provided by the AgentPay x402 — Economic-intelligence layer for AI Agents MCP server (romudille-bit/agentpay). 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 →