AI agents call recording_cancel to permanently remove resources in ScreenHand — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a recording without saving irreversibly discards the recorded data. The recording cannot be recovered after cancellation, making this a destructive action. Severity is medium since it only affects the current recording session rather than broader system data.
From the tool's definition Cancel the current recording without saving
Documented attack patterns abuse exactly the kind of access recording_cancel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScreenHand, and nothing reaches the server without passing your rules. This is the rule we recommend for recording_cancel:
{
"version": "1",
"default": "deny",
"hide": [
"recording_cancel"
]
}recording_cancel 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.
Cancel the current recording without saving. It is categorised as a Destructive tool in the ScreenHand MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScreenHand MCP server in PolicyLayer and add a rule for recording_cancel: 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 ScreenHand. Nothing to install.
recording_cancel 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 recording_cancel 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 recording_cancel. 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.
recording_cancel is provided by the ScreenHand MCP server (manushi4/screenhand). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScreenHand, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 ScreenHand tools catalogued and risk-classified — across an index of 43,000+ MCP servers.