This record as markdown: /tools/openclaw/path.md
What path does on OpenClaw
AI agents use path 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 path is rated Medium
The 'edit' capability indicates this tool can modify files, making it a Write operation. While 'inspect' suggests read access, the explicit mention of editing workspace files is the primary concern—file modifications are reversible but can corrupt or alter critical workspace state. Severity is high because uncontrolled file editing in a workspace context could affect project integrity, configuration, or data.
From the tool's definition Tool description states 'Inspect and edit workspace files via oc:// paths' — explicitly mentions both read ('Inspect') and write ('edit') capabilities on workspace files.
Attacks that exploit this kind of access
The rule that runs path 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 path, this is the rule to start with:
path 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 path call is checked against it from then on.
Questions about path
Inspect and edit workspace files via oc:// paths. 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 path: 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.
path 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 path 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 path. 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.
path 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