unclick_resize_image
Resize an image (provided as base64) to specified dimensions.
This record as markdown: /tools/creativelead-unclick/unclick-resize-image.md
What unclick_resize_image does on UnClick
AI agents use unclick_resize_image to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
fit | string | — | |
image | string | — | Base64-encoded image (with or without data: prefix) |
width | number | — | |
height | number | — |
Parameters from the server's own tool schema.
Why unclick_resize_image is rated Medium
The tool modifies image data by resizing it to new dimensions. While this is reversible (the original can be retained or re-resized), it constitutes a Write operation as it transforms and outputs modified data. The operation has minimal blast radius—worst case being distorted or incorrect image dimensions—and no destructive, financial, or dangerous execute-level consequences.
From the tool's definition Tool description states: 'Resize an image (provided as base64) to specified dimensions.' This performs image transformation and modification.
Attacks that exploit this kind of access
The rule that runs unclick_resize_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unclick_resize_image, this is the rule to start with:
unclick_resize_image stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every unclick_resize_image call is checked against it from then on.
Questions about unclick_resize_image
Resize an image (provided as base64) to specified dimensions. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
unclick_resize_image accepts 4 parameters: fit, image, width, height. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for unclick_resize_image: 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 UnClick. Nothing to install.
unclick_resize_image is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unclick_resize_image 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 unclick_resize_image. 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.
unclick_resize_image is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue