This record as markdown: /tools/openclaw/pair.md
What pair does on OpenClaw
AI agents use pair to create or update resources in OpenClaw, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenClaw environment.
Why pair is rated Medium
The ability to approve device pairing requests is a Write operation that creates reversible device trust relationships. While it doesn't delete data or execute arbitrary code, it does modify authentication/authorization state. Severity is medium because misuse could grant unauthorized device access to a system, though the impact scope depends on what those paired devices can subsequently do.
From the tool's definition Tool can 'Generate setup codes and approve device pairing requests' - this modifies system state by approving pairing requests, which creates new trusted device relationships in the system.
Attacks that exploit this kind of access
The rule that runs pair 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 pair, this is the rule to start with:
pair 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.
The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every pair call is checked against it from then on.
Questions about pair
Generate setup codes and approve device pairing requests. It is categorised as a Write tool in the OpenClaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenClaw MCP server in PolicyLayer and add a rule for pair: 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.
pair 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 pair 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 pair. 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.
pair 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.
More on OpenClaw, and thousands of servers like it.
This server
Across the catalogue