Clear rendered scrollback history while preserving current screen.
AI agents call clear_scrollback to permanently remove resources in PiloTY — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys terminal scrollback buffer history. The data (previous terminal output) cannot be recovered once cleared. While the blast radius is limited to terminal history rather than system data, it is an irreversible deletion action, making Destructive the appropriate category.
From the tool's definition Clear rendered scrollback history
Documented attack patterns abuse exactly the kind of access clear_scrollback gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PiloTY, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_scrollback:
{
"version": "1",
"default": "deny",
"hide": [
"clear_scrollback"
]
}clear_scrollback disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear rendered scrollback history while preserving current screen. It is categorised as a Destructive tool in the PiloTY MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PiloTY MCP server in PolicyLayer and add a rule for clear_scrollback: 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 PiloTY. Nothing to install.
clear_scrollback is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_scrollback 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 clear_scrollback. 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.
clear_scrollback is provided by the PiloTY MCP server (yiwenlu66/piloty). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 PiloTY tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 PiloTY tools catalogued and risk-classified — across an index of 42,500+ MCP servers.