Scan a smart contract for honeypot detection, rug pull indicators (mint functions, blacklists, fee manipulation, proxy patterns), and source verification status.
AI agents call contract_scan to retrieve information from Mcp Services without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
contract_scan is purely analytical: it examines contract bytecode, source code, and on-chain metadata to report findings about risk patterns. It performs no state-modifying operations (no transactions, deployments, transfers, or deletions). While it queries blockchain data, the query itself has no side effects—it is read-only intelligence gathering.
From the tool's definition Tool description states 'scan' and 'detection'—it analyzes smart contract code and metadata for security indicators (honeypot, rug pull patterns, verification status) without modifying any blockchain state, contract, or external data.
Attacks that exploit this kind of access
Scan a smart contract for honeypot detection, rug pull indicators (mint functions, blacklists, fee manipulation, proxy patterns), and source verification status. It is categorised as a Read tool in the Mcp Services MCP Server, which means it retrieves data without modifying state.
Register the Mcp Services MCP server in PolicyLayer and add a rule for contract_scan: 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 Mcp Services. Nothing to install.
contract_scan 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 contract_scan 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 contract_scan. 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.
contract_scan is provided by the Mcp Services MCP server (san-npm/mcp-services). 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 →