open_path · Sysprobe MCP: Risk & Policy

WHAT IT DOES

What open_path does on Sysprobe

AI agents invoke open_path to trigger actions in Sysprobe. 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 IT NEEDS A POLICY

Why open_path needs a policy

This tool executes xdg-open which launches an external application or handler. The effects depend on what path/URL is passed — it could open a browser, run a document viewer, or trigger other applications. This is an Execute-category action since it triggers external operations whose effects depend on arguments, not merely reading or writing data directly.

From the tool's definition Open a file/folder/URL with the default handler (xdg-open)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sysprobe, so you can run agents against it safely.

FAQ

Questions about open_path

What does the open_path tool do? +

[ACTION] Open a file/folder/URL with the default handler (xdg-open). It is categorised as a Execute tool in the Sysprobe 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 Sysprobe 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 Sysprobe. 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 Sysprobe MCP server (raindancer118/sysprobe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.