Scroll the page or a specific element. Supports direction (up/down/left/right) and pixel amount. Can target a scrollable container by a11yRef, testId, or CSS selector.
Part of the Tronlink server.
Free to start. No card required.
AI agents use tl_scroll to create or modify resources in Tronlink. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call tl_scroll repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Tronlink.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"tl_scroll": {
"limits": [
{
"counter": "tl_scroll_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Tronlink policy for all 55 tools.
These attack patterns abuse exactly the kind of access tl_scroll gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Scroll the page or a specific element. Supports direction (up/down/left/right) and pixel amount. Can target a scrollable container by a11yRef, testId, or CSS selector.. It is categorised as a Write tool in the Tronlink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tronlink MCP server in PolicyLayer and add a rule for tl_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 Tronlink. Nothing to install.
tl_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 tl_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 tl_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.
tl_scroll is provided by the Tronlink MCP server (@tronlink/mcp-server-tronlink). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 55 Tronlink tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.