Scroll the page in the specified direction
AI agents use scroll to create or update resources in AutoProbeMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoProbeMCP environment.
An AI agent can call scroll faster than any human can review — one bad instruction and it creates or modifies resources in AutoProbeMCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Scroll the page in the specified direction. It is categorised as a Write tool in the AutoProbeMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoProbe 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 AutoProbeMCP. Nothing to install.
scroll is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 AutoProbe MCP server (wladastic/autoprobemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.