Critical Risk →

photopea_clear_selection

Deselect the current selection in the active document, removing the marching ants. Does not modify any pixel data. Use after fill_selection or other selection-based operations are complete.

Part of the Photopea MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

photopea-mcp-server Destructive Risk 4/5

AI agents may call photopea_clear_selection to permanently remove or destroy resources in Photopea. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call photopea_clear_selection in a loop, permanently destroying resources in Photopea. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

photopea.yaml
tools:
  photopea_clear_selection:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Photopea policy for all 34 tools.

Tool Name photopea_clear_selection
Category Destructive
MCP Server Photopea MCP Server
Risk Level Critical

View all 34 tools →

Agents calling destructive-class tools like photopea_clear_selection have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

photopea_clear_selection is one of the critical-risk operations in Photopea. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the photopea_clear_selection tool do? +

Deselect the current selection in the active document, removing the marching ants. Does not modify any pixel data. Use after fill_selection or other selection-based operations are complete.. It is categorised as a Destructive tool in the Photopea MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on photopea_clear_selection? +

Add a rule in your Intercept YAML policy under the tools section for photopea_clear_selection. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Photopea MCP server.

What risk level is photopea_clear_selection? +

photopea_clear_selection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit photopea_clear_selection? +

Yes. Add a rate_limit block to the photopea_clear_selection rule in your Intercept 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.

How do I block photopea_clear_selection completely? +

Set action: deny in the Intercept policy for photopea_clear_selection. 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.

What MCP server provides photopea_clear_selection? +

photopea_clear_selection is provided by the Photopea MCP server (photopea-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Photopea

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.