browser_scroll
A write tool on the MCP Framework Personal MCP server.
This record as markdown: /tools/inggerman-mcps/browser-scroll.md
What browser_scroll does on MCP Framework Personal
AI agents use browser_scroll to create or update resources in MCP Framework Personal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Framework Personal environment.
Why browser_scroll is rated Medium
An AI agent can call browser_scroll faster than any human can review: one bad instruction and it creates or modifies resources in MCP Framework Personal by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs browser_scroll safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_scroll, this is the rule to start with:
browser_scroll stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every browser_scroll call is checked against it from then on.
Questions about browser_scroll
browser_scroll is a write tool on the MCP Framework Personal MCP server. It is categorised as a Write tool in the MCP Framework Personal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for browser_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 MCP Framework Personal. Nothing to install.
browser_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 browser_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 browser_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.
browser_scroll is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue