AI agents use image_convert to create or update resources in Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tools environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Image URL to convert |
width | number | — | Target width in pixels |
format | string | — | Output format (default: webp) |
height | number | — | Target height in pixels |
quality | number | — | Quality 1-100 (default: 80) |
Parameters from the server's own tool schema.
image_convert creates new image files or modifies existing ones through format conversion, resizing, and quality adjustment. These are reversible operations—the original file is not destroyed, and the output can be regenerated or reverted. This is fundamentally a data transformation/creation tool rather than a read-only operation.
From the tool's definition Tool performs image format conversion with resize and quality control capabilities. The description indicates it creates or modifies image data (converts formats, applies transformations), which are reversible operations typical of Write category tools.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Convert image format to WebP/AVIF/PNG/JPEG with optional resize and quality control. It is categorised as a Write tool in the Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
image_convert accepts 5 parameters: url, width, format, height, quality. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for image_convert: 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 Tools. Nothing to install.
image_convert 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 image_convert 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 image_convert. 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.
image_convert is provided by the Tools MCP server (https://www.jiebang.site/mcp). 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 →