AI agents use disconnect to create or update resources in MetaMask MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MetaMask MCP environment.
Disconnecting a wallet is a Write operation because it changes the state of the wallet connection (from connected to disconnected). It is reversible, as the wallet can be reconnected. The severity is low because disconnection has no blast radius on blockchain assets, transactions, or data — it merely terminates the session without causing financial loss, data destruction, or irreversible changes.
From the tool's definition Tool description states 'Disconnect the wallet' — a reversible state change operation that modifies the connection status of the wallet.
Documented attack patterns abuse exactly the kind of access disconnect 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 disconnect:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect": {
"limits": [
{
"counter": "disconnect_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disconnect stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disconnect the wallet. It is categorised as a Write tool in the MetaMask MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MetaMask MCP server in PolicyLayer and add a rule for disconnect: 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.
disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect 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 disconnect. 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.
disconnect 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.