demo_load_actions

Resume editing a previously saved script instead of rehearsing from scratch.

SERVERDemoday Claude Plugin SOURCEmrieck/demoday-claude-plugin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/demoday-claude-plugin/demo-load-actions.md

WHAT IT DOES

What demo_load_actions does on Demoday Claude Plugin

AI agents call demo_load_actions to retrieve information from Demoday Claude Plugin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why demo_load_actions is rated Low

Loads and retrieves existing script data without modification or side effects.

From the tool's definition Resume editing a previously saved script instead of rehearsing

Attacks that exploit this kind of access

RECOMMENDED RULE

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

demo_load_actions Allowed

demo_load_actions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "demo_load_actions": {}
  }
}

ALLOW ONLY 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_load_actions call is checked against it from then on.

FAQ

Questions about demo_load_actions

What does the demo_load_actions tool do? +

Resume editing a previously saved script instead of rehearsing from scratch. It is categorised as a Read tool in the Demoday Claude Plugin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on demo_load_actions? +

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

demo_load_actions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit demo_load_actions? +

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

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

demo_load_actions 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →