auditContract

A read tool on the Ethereum Tools MCP server.

SERVEREthereum Tools SOURCE0xgval/evm-mcp-tools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/0xgval-evm-mcp-tools/auditcontract.md

WHAT IT DOES

What auditContract does on Ethereum Tools

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

RISK

Why auditContract is rated Low

The 'audit' prefix suggests static analysis or inspection of smart contract code and security properties. The server explicitly advertises 'contract auditing' alongside read-focused functions like balance checks and transaction analysis. No evidence suggests code execution, contract modification, or fund movement.

From the tool's definition Tool named 'auditContract' with empty description. Based on server context describing 'contract auditing' as a core capability and sibling tools being read-only analysis functions (getEthBalance, getTokenInfo, getTokenPriceHistory, getWalletPnl,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auditContract safely

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

auditContract Allowed

auditContract 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": {
    "auditContract": {}
  }
}

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

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

FAQ

Questions about auditContract

What does the auditContract tool do? +

auditContract is a read tool on the Ethereum Tools MCP server. It is categorised as a Read tool in the Ethereum Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on auditContract? +

Register the Ethereum Tools MCP server in PolicyLayer and add a rule for auditContract: 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 Ethereum Tools. Nothing to install.

What risk level is auditContract? +

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

Can I rate-limit auditContract? +

Yes. Add a rate_limit block to the auditContract 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 auditContract completely? +

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

auditContract is provided by the Ethereum Tools MCP server (0xgval/evm-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ethereum Tools, and thousands of servers like it.

This server

All 11 Ethereum Tools tools →

Across the catalogue

The MCP Attack Database →

Guides

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