demo_scroll
Smooth eased scroll by dy pixels (negative scrolls up). Records the step.
This record as markdown: /tools/demoday-claude-plugin/demo-scroll.md
What demo_scroll does on Demoday Claude Plugin
AI agents invoke demo_scroll 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.
Why demo_scroll is rated High
Executes browser scroll action and records it as part of demo automation.
From the tool's definition Smooth eased scroll by dy pixels. Records the step.
Attacks that exploit this kind of access
The rule that runs demo_scroll 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_scroll, this is the rule to start with:
demo_scroll 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Demoday Claude Plugin, apply this rule, and every demo_scroll call is checked against it from then on.
Questions about demo_scroll
Smooth eased scroll by dy pixels (negative scrolls up). Records the step. 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.
Register the Demoday Claude Plugin MCP server in PolicyLayer and add a rule for demo_scroll: 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.
demo_scroll is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the demo_scroll 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.
Set action: deny in the PolicyLayer policy for demo_scroll. 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.
demo_scroll 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.
More on Demoday Claude Plugin, and thousands of servers like it.
Across the catalogue