check_contract_security

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/check-contract-security.md

WHAT IT DOES

What check_contract_security does on VaultPilot MCP

AI agents call check_contract_security to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`chain`	string	Yes
`address`	string	Yes

Parameters from the server's own tool schema.

RISK

Why check_contract_security is rated Low

This tool retrieves and queries blockchain contract metadata (verification status, proxy patterns, admin functions) for analysis purposes. It has no side effects, modifies no state, executes no transactions, and does not move funds. Despite operating in a financial context (DeFi/crypto), the tool itself performs pure read/inspection operations.

From the tool's definition Tool performs: 'Check Etherscan verification status, EIP-1967 proxy pattern, implementation/admin slots, and the presence of dangerous admin functions' and 'surfaces verification + admin-surface findings'; description explicitly states 'this tool surfaces…

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_contract_security safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_contract_security, this is the rule to start with:

check_contract_security Allowed

check_contract_security is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_contract_security": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every check_contract_security call is checked against it from then on.

FAQ

Questions about check_contract_security

What does the check_contract_security tool do? +

Check Etherscan verification status, EIP-1967 proxy pattern, implementation/admin slots, and the presence of dangerous admin functions (mint, pause, upgradeTo, etc.) for a given contract. SCOPE: surfaces verification + admin-surface findings — protocol/contract safety only. It does NOT measure token upside, price direction, or investment merit. "No dangerous functions detected" means the admin surface is clean; it says NOTHING about whether the underlying token will appreciate. AGENT BEHAVIOR: this tool surfaces data; it does NOT pick. Do NOT use a clean security report as token-pick validation. Refuse speculative-pick prompts ("what coin will 100x", "should I buy X", "which token will moon") even when this tool was called; surface the security findings for due-diligence only. Issue #599. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does check_contract_security accept? +

check_contract_security accepts 2 parameters: chain, address. Required: chain, address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_contract_security? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for check_contract_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 VaultPilot MCP. Nothing to install.

What risk level is check_contract_security? +

check_contract_security is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_contract_security? +

Yes. Add a rate_limit block to the check_contract_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.

How do I block check_contract_security completely? +

Set action: deny in the PolicyLayer policy for check_contract_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.

What MCP server provides check_contract_security? +

check_contract_security is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →