open_4d_command_in_browser · 4D Documentation Viewer MCP

WHAT IT DOES

What open_4d_command_in_browser does on 4D Documentation Viewer

AI agents invoke open_4d_command_in_browser to trigger actions in 4D Documentation Viewer. 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_4d_command_in_browser needs a policy

This tool triggers an external operation (opening a URL in the system's default web browser), which is an Execute-category action. It does not read/write data in a traditional sense but invokes a system-level action. The blast radius is low as it only opens a documentation webpage.

From the tool's definition Open a 4D command documentation page in the default web browser. This opens the URL https://developer.4d.com/docs/commands/<command-name> directly in your browser.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

open_4d_command_in_browser Rate-limited

open_4d_command_in_browser 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_4d_command_in_browser": {
      "limits": [
        {
          "counter": "open_4d_command_in_browser_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 4D Documentation Viewer, so you can run agents against it safely.

FAQ

Questions about open_4d_command_in_browser

What does the open_4d_command_in_browser tool do? +

Open a 4D command documentation page in the default web browser. This opens the URL https://developer.4d.com/docs/commands/<command-name> directly in your browser. It is categorised as a Execute tool in the 4D Documentation Viewer 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_4d_command_in_browser? +

Register the 4D Documentation Viewer MCP server in PolicyLayer and add a rule for open_4d_command_in_browser: 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 4D Documentation Viewer. Nothing to install.

What risk level is open_4d_command_in_browser? +

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

Can I rate-limit open_4d_command_in_browser? +

Yes. Add a rate_limit block to the open_4d_command_in_browser 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_4d_command_in_browser completely? +

Set action: deny in the PolicyLayer policy for open_4d_command_in_browser. 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_4d_command_in_browser? +

open_4d_command_in_browser is provided by the 4D Documentation Viewer MCP server (mesopelagique/mcp-4d-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.