This record as markdown: /tools/openclaw/auth.md
What auth does on OpenClaw
AI agents invoke auth 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 auth is rated High
This tool triggers authentication flows with external providers, which constitutes executing an operation with side effects (establishing auth sessions, tokens, credentials). While not as severe as arbitrary code execution, it could allow an agent to authenticate as a user to external services or escalate privileges depending on the provider and flow.
From the tool's definition Tool description states 'Run provider auth/login flow' - the verb 'Run' indicates execution of an external authentication operation whose effects depend on which provider is targeted.
Attacks that exploit this kind of access
The rule that runs auth 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 auth, this is the rule to start with:
auth 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 auth call is checked against it from then on.
Questions about auth
Run provider auth/login flow. 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 auth: 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.
auth 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 auth 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 auth. 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.
auth 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