Returns the success or error status of a contract verification request.
AI agents call contract__checkverifystatus to retrieve information from Etherscan MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain data to retrieve the status of a contract verification request. It performs no modifications, deletions, executions, or financial operations. It is a straightforward read operation consistent with the other account and contract query tools on the Etherscan MCP server. The low severity reflects minimal blast radius — retrieving verification status cannot harm data or systems.
From the tool's definition Tool description states it 'Returns the success or error status of a contract verification request' — a pure retrieval operation with no side effects. The verb 'Returns' and the context of checking status indicate a query operation.
Documented attack patterns abuse exactly the kind of access contract__checkverifystatus gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Etherscan MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for contract__checkverifystatus:
{
"version": "1",
"default": "deny",
"tools": {
"contract__checkverifystatus": {}
}
} contract__checkverifystatus is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the success or error status of a contract verification request. It is categorised as a Read tool in the Etherscan MCP MCP Server, which means it retrieves data without modifying state.
Register the Etherscan MCP server in PolicyLayer and add a rule for contract__checkverifystatus: 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 Etherscan MCP. Nothing to install.
contract__checkverifystatus 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__checkverifystatus 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__checkverifystatus. 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__checkverifystatus is provided by the Etherscan MCP server (xiaok/etherscan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Etherscan MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
56 Etherscan MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.