demo_open

Launch a browser for rehearsal and start a new action script. Nothing is

SERVERDemoday Claude Plugin SOURCEmrieck/demoday-claude-plugin

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/demoday-claude-plugin/demo-open.md

WHAT IT DOES

What demo_open does on Demoday Claude Plugin

AI agents invoke demo_open to trigger actions in Demoday Claude Plugin. 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 demo_open is rated High

Launches a browser instance and initiates a new script, triggering external operations.

From the tool's definition Launch a browser for rehearsal and start a new action script

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs demo_open safely

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

demo_open Rate-limited

demo_open 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": {
    "demo_open": {
      "limits": [
        {
          "counter": "demo_open_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 Demoday Claude Plugin, apply this rule, and every demo_open call is checked against it from then on.

FAQ

Questions about demo_open

What does the demo_open tool do? +

Launch a browser for rehearsal and start a new action script. Nothing is. It is categorised as a Execute tool in the Demoday Claude Plugin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on demo_open? +

Register the Demoday Claude Plugin MCP server in PolicyLayer and add a rule for demo_open: 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 Demoday Claude Plugin. Nothing to install.

What risk level is demo_open? +

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

Can I rate-limit demo_open? +

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

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

demo_open is provided by the Demoday Claude Plugin MCP server (mrieck/demoday-claude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Demoday Claude Plugin, and thousands of servers like it.

This server

All 16 Demoday Claude Plugin 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 →