get-connect-uri

THE RISK

Low Risk

Why get-connect-uri needs a policy

This tool returns a URI string needed for wallet connection establishment. It performs no blockchain transactions, fund movements, contract deployments, or data modifications. It is purely informational, making it a Read category tool with low severity since misuse would only expose connection information without enabling malicious transactions (which require additional tool usage like 'call' or 'deploy-contract').

From the tool's definition The tool name 'get-connect-uri' and description 'Get the connect URI to connect to a MetaMask wallet' indicate a retrieval operation.

Documented attack patterns abuse exactly the kind of access get-connect-uri gives an agent:

POLICY

How to control get-connect-uri

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 get-connect-uri:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-connect-uri": {}
  }
}

get-connect-uri is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MetaMask MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MetaMask MCP tools

Financial send-transaction Send transactions to networks. Execute deploy-contract Deploy a contract to the network, given bytecode, and constructor arguments. Execute call Executing a new message call immediately without submitting a transaction to the network. Execute sign-message Sign a message. Execute switch-chain Switch the target chain. Execute write-contract Execute a write function on a contract. Write disconnect Disconnect the wallet. Read wait-for-transaction-receipt Waits for the transaction to be included on a block, and then returns the transaction rece

All 29 MetaMask MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-connect-uri

What does the get-connect-uri tool do? +

Get the connect URI to connect to a MetaMask wallet. It is categorised as a Read tool in the MetaMask MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-connect-uri? +

Register the MetaMask MCP server in PolicyLayer and add a rule for get-connect-uri: 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.

What risk level is get-connect-uri? +

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

Can I rate-limit get-connect-uri? +

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

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

get-connect-uri 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.

Enforce policy on every MetaMask MCP tool call.

Start from MetaMask MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →