Scale, rotate, or flip a layer in-place. Modifies the layer's pixel data destructively. Use get_layers to check current layer bounds before transforming, and undo to revert if needed.
Part of the Photopea MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke photopea_transform_layer to trigger processes or run actions in Photopea. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
photopea_transform_layer can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
photopea_transform_layer:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Photopea policy for all 34 tools.
Agents calling execute-class tools like photopea_transform_layer have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
photopea_transform_layer is one of the high-risk operations in Photopea. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Scale, rotate, or flip a layer in-place. Modifies the layer's pixel data destructively. Use get_layers to check current layer bounds before transforming, and undo to revert if needed.. It is categorised as a Execute tool in the Photopea MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for photopea_transform_layer. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Photopea MCP server.
photopea_transform_layer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the photopea_transform_layer 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.
Set action: deny in the Intercept policy for photopea_transform_layer. 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.
photopea_transform_layer 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.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept