show-connect-qrcode

THE RISK

Low Risk

Why show-connect-qrcode needs a policy

This tool retrieves and displays a QR code artifact used for connection initiation. It has no side effects on blockchain state, user accounts, or wallet operations. While the MetaMask server overall enables financial operations (transactions via sibling tools like call and deploy-contract), this specific tool is purely informational and read-only.

From the tool's definition The tool displays a QR code for a connection URI—a retrieval and presentation operation with no state modification. The description states it will 'show' the QR code, which is a read/display action.

Documented attack patterns abuse exactly the kind of access show-connect-qrcode gives an agent:

POLICY

How to control show-connect-qrcode

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 show-connect-qrcode:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "show-connect-qrcode": {}
  }
}

show-connect-qrcode 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 show-connect-qrcode

What does the show-connect-qrcode tool do? +

Show the connect QR code for a given connect URI. 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 show-connect-qrcode? +

Register the MetaMask MCP server in PolicyLayer and add a rule for show-connect-qrcode: 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 show-connect-qrcode? +

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

Can I rate-limit show-connect-qrcode? +

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

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

show-connect-qrcode 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 →