open_path

Open a file or folder with the system default application

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/open-path.md

WHAT IT DOES

What open_path does on CoWork OS

AI agents invoke open_path to trigger actions in CoWork OS. 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.

RISK

Why open_path is rated High

This tool triggers external application launches by opening files/folders with system default apps. The effect depends on the path argument — opening a script could execute it, opening a document launches an external application. This is an external operation trigger, not a simple read, making Execute the most appropriate category.

From the tool's definition Open a file or folder with the system default application

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs open_path safely

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

open_path Rate-limited

open_path 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "open_path": {
      "limits": [
        {
          "counter": "open_path_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about open_path

What does the open_path tool do? +

Open a file or folder with the system default application. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_path? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for open_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 CoWork OS. Nothing to install.

What risk level is open_path? +

open_path is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit open_path? +

Yes. Add a rate_limit block to the open_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.

How do I block open_path completely? +

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

What MCP server provides open_path? +

open_path is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →