Delete a screenshot configuration and all captured screenshots.
AI agents call delete_screenshot_config to permanently remove resources in PagePixels Screenshots MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes both configuration records and all associated captured screenshots. Deletion is an irreversible operation with no recovery mechanism described.
From the tool's definition The tool description states it will 'Delete a screenshot configuration and all captured screenshots' — the verb 'delete' combined with 'all' indicates irreversible removal of data that cannot be undone.
Attacks that exploit this kind of access
Delete a screenshot configuration and all captured screenshots. It is categorised as a Destructive tool in the PagePixels Screenshots MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PagePixels Screenshots MCP Server MCP server in PolicyLayer and add a rule for delete_screenshot_config: 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 PagePixels Screenshots MCP Server. Nothing to install.
delete_screenshot_config 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 delete_screenshot_config 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 delete_screenshot_config. 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.
delete_screenshot_config is provided by the PagePixels Screenshots MCP Server MCP server (pagepixels/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →