# demo_open_app

Prepare the macOS desktop for a demo of a native, Electron or terminal app:

Agent View of the PolicyLayer registry record for `demo_open_app`. HTML page: https://policylayer.com/tools/demoday-claude-plugin/demo-open-app

## Facts

- Tool: `demo_open_app`
- Server: Demoday Claude Plugin (`mrieck/demoday-claude-plugin`) — https://policylayer.com/tools/demoday-claude-plugin.md
- Homepage: https://github.com/mrieck/demoday-claude-plugin
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "demo_open_app",
    "arguments": {}
  }
}
```

## Why demo_open_app is rated High

Triggers OS-level desktop preparation, executing external operations on the system environment.

From the tool's own definition: "Prepare the macOS desktop for a demo of a native app"

## Use case

AI agents invoke demo_open_app 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Demoday Claude Plugin:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "demo_open_app": {
      "limits": [
        {
          "counter": "demo_open_app_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Demoday Claude Plugin (15)

- `demo_undo_step` — Destructive — https://policylayer.com/tools/demoday-claude-plugin/demo-undo-step.md
- `demo_click` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-click.md
- `demo_highlight` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-highlight.md
- `demo_key` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-key.md
- `demo_open` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-open.md
- `demo_open_cli` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-open-cli.md
- `demo_scroll` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-scroll.md
- `demo_type` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-type.md
- `demo_wait_stable` — Execute — https://policylayer.com/tools/demoday-claude-plugin/demo-wait-stable.md
- `demo_inspect` — Read — https://policylayer.com/tools/demoday-claude-plugin/demo-inspect.md
- `demo_load_actions` — Read — https://policylayer.com/tools/demoday-claude-plugin/demo-load-actions.md
- `demo_screenshot` — Read — https://policylayer.com/tools/demoday-claude-plugin/demo-screenshot.md
- `demo_close` — Write — https://policylayer.com/tools/demoday-claude-plugin/demo-close.md
- `demo_review_script` — Write — https://policylayer.com/tools/demoday-claude-plugin/demo-review-script.md
- `demo_save_actions` — Write — https://policylayer.com/tools/demoday-claude-plugin/demo-save-actions.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=demoday-claude-plugin · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/demoday-claude-plugin