phone
Arm/disarm high-risk phone node commands (camera/screen/writes).
This record as markdown: /tools/openclaw/phone.md
What phone does on OpenClaw
AI agents invoke phone to trigger actions in OpenClaw. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why phone is rated High
This tool controls arming and disarming of high-risk commands on a phone node, including camera access, screen capture, and write operations. These are privileged device-level capabilities. The 'arm/disarm' framing means it enables or disables execution of these sensitive operations.
From the tool's definition Arm/disarm high-risk phone node commands (camera/screen/writes)
Attacks that exploit this kind of access
The rule that runs phone 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 phone, this is the rule to start with:
phone stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 phone call is checked against it from then on.
Questions about phone
Arm/disarm high-risk phone node commands (camera/screen/writes). It is categorised as a Execute tool in the OpenClaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenClaw MCP server in PolicyLayer and add a rule for phone: 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.
phone is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the phone 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 phone. 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.
phone 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.
Across the catalogue