Scroll page up or down by pixel amount. Use to reveal content below the fold or navigate long pages.
AI agents invoke scroll to trigger actions in Camofox. 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.
Scrolling is a browser interaction that executes a UI action. While it has minimal blast radius and no data modification, it is an active browser operation (not a passive read) that can reveal content, trigger lazy-loaded elements, or cause side effects on dynamic pages. In the context of an anti-detection automation server, it is classified as Execute. Severity is low as scrolling alone causes minimal harm.
From the tool's definition 'Scroll page up or down by pixel amount' — triggers a browser action that manipulates the viewport/page state
Documented attack patterns abuse exactly the kind of access scroll gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camofox, and nothing reaches the server without passing your rules. This is the rule we recommend for scroll:
{
"version": "1",
"default": "deny",
"tools": {
"scroll": {
"limits": [
{
"counter": "scroll_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Scroll page up or down by pixel amount. Use to reveal content below the fold or navigate long pages. It is categorised as a Execute tool in the Camofox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Camofox MCP server in PolicyLayer and add a rule for 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 Camofox. Nothing to install.
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 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 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.
scroll is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.