demo_click

Click by selector (preferred — pass the ladder from demo_inspect) or by page

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-click.md

WHAT IT DOES

What demo_click does on Demoday Claude Plugin

AI agents invoke demo_click 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_click is rated High

Triggers browser click actions, executing UI interactions with variable effects.

From the tool's definition Click by selector or by page

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs demo_click 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_click, this is the rule to start with:

demo_click Rate-limited

demo_click 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_click": {
      "limits": [
        {
          "counter": "demo_click_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_click call is checked against it from then on.

FAQ

Questions about demo_click

What does the demo_click tool do? +

Click by selector (preferred — pass the ladder from demo_inspect) or by page. 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_click? +

Register the Demoday Claude Plugin MCP server in PolicyLayer and add a rule for demo_click: 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_click? +

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

Can I rate-limit demo_click? +

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

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

demo_click 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

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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