Verify that a message was signed by the provided address.
AI agents call verify-message to retrieve information from MetaMask MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs signature verification, which is a deterministic read operation that queries whether a given signature matches a provided address and message. It retrieves or validates existing data without modifying, executing external code, deleting, or moving funds. No state is changed and no external operations are triggered.
From the tool's definition Tool description states 'Verify that a message was signed by the provided address' — a purely read-only cryptographic validation operation with no side effects, state changes, or external actions.
Documented attack patterns abuse exactly the kind of access verify-message 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 verify-message:
{
"version": "1",
"default": "deny",
"tools": {
"verify-message": {}
}
}verify-message 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.
Verify that a message was signed by the provided address. It is categorised as a Read tool in the MetaMask MCP MCP Server, which means it retrieves data without modifying state.
Register the MetaMask MCP server in PolicyLayer and add a rule for verify-message: 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.
verify-message 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 verify-message 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 verify-message. 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.
verify-message 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.