eth_compile_contract · Portal MCP: Risk & Policy

WHAT IT DOES

What eth_compile_contract does on PortalMCP

AI agents invoke eth_compile_contract to trigger actions in PortalMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why eth_compile_contract needs a policy

While compilation itself is reversible and produces only data artifacts (bytecode/ABI), it executes a compiler process that processes arbitrary code. In the blockchain context where this tool operates alongside contract deployment capabilities, compiling untrusted or malicious contract code could be chained with deployment tools to cause harm.

From the tool's definition Tool performs 'compile' action on Solidity contract code, producing bytecode and ABI. Compilation is a code execution operation that transforms source code into executable form.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

eth_compile_contract Rate-limited

eth_compile_contract stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "eth_compile_contract": {
      "limits": [
        {
          "counter": "eth_compile_contract_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PortalMCP, so you can run agents against it safely.

FAQ

Questions about eth_compile_contract

What does the eth_compile_contract tool do? +

Compile Solidity contract code to bytecode and ABI. It is categorised as a Execute tool in the PortalMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on eth_compile_contract? +

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

What risk level is eth_compile_contract? +

eth_compile_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit eth_compile_contract? +

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

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

eth_compile_contract is provided by the Portal MCP server (portalfnd/portalmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.