qr

Generate mobile pairing QR/setup code

SERVEROpenClaw SOURCEopenclaw

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/openclaw/qr.md

WHAT IT DOES

What qr does on OpenClaw

AI agents call qr as a supporting operation in OpenClaw workflows.

RISK

Why qr is rated Low

This tool generates a QR code or setup code for mobile pairing. It appears to produce a visual/data artifact for device pairing purposes. This is closest to 'Read' or 'Other' — it doesn't retrieve existing data, modify state, execute code, delete data, or move money. It generates a pairing code, which is a setup/display operation.

From the tool's definition Generate mobile pairing QR/setup code

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs qr safely

PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For qr, this is the rule to start with:

qr Rate-limited

qr gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qr": {
      "limits": [
        {
          "counter": "qr_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every qr call is checked against it from then on.

FAQ

Questions about qr

What does the qr tool do? +

Generate mobile pairing QR/setup code. It is categorised as a Other tool in the OpenClaw MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on qr? +

Register the OpenClaw MCP server in PolicyLayer and add a rule for qr: 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 OpenClaw. Nothing to install.

What risk level is qr? +

qr is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit qr? +

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

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

qr is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on OpenClaw, and thousands of servers like it.

This server

All 129 OpenClaw tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →