Deploy a contract to the network, given bytecode, and constructor arguments.
AI agents invoke deploy-contract to trigger actions in MetaMask MCP. 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.
While contract deployment is technically write-like (creating new data), it is classified as Execute because: (1) it runs arbitrary code (the deployed bytecode) on a public ledger, (2) the effects are unpredictable and depend entirely on the bytecode argument, (3) deployment is effectively irreversible in practice (code cannot be deleted, only abandoned), and (4) it can facilitate financial crimes or drain user…
From the tool's definition Tool description states it 'Deploy a contract to the network, given bytecode, and constructor arguments.' Deployment of smart contracts is an irreversible execution action that creates immutable code on a blockchain and can trigger arbitrary effects (token…
Documented attack patterns abuse exactly the kind of access deploy-contract gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MetaMask MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy-contract:
{
"version": "1",
"default": "deny",
"tools": {
"deploy-contract": {
"limits": [
{
"counter": "deploy-contract_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}deploy-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.
Free to start. No card required.
Deploy a contract to the network, given bytecode, and constructor arguments. It is categorised as a Execute tool in the MetaMask MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MetaMask MCP server in PolicyLayer and add a rule for deploy-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 MetaMask MCP. Nothing to install.
deploy-contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy-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.
Set action: deny in the PolicyLayer policy for deploy-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.
deploy-contract is provided by the MetaMask MCP server (xiawpohr/metamask-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MetaMask 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.
29 MetaMask MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.