image_resize

SERVERTanod SOURCEhttps://tanod.dev/mcp

Medium RISK CLASS

Category Write

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/image-resize.md

WHAT IT DOES

What image_resize does on Tanod

AI agents use image_resize to create or update resources in Tanod, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tanod environment.

Parameter	Type	Required	Description
`fit`	string	—	With width and height: inside (default; fit within, keep aspect), contain (fit within, padded to the exact box), cover (fill the box, centre crop) or fill (stre
`url`	object	—	Public http(s) URL of the image (at most 10 MB; private, internal and IP-literal hosts are refused); or use image_base64.
`scale`	object	—	Instead of width/height.
`width`	object	—	Target width in pixels (1-32768); give width, height, both, or scale.
`format`	object	—	Output format (default: the input's; ICO in, PNG out).
`height`	object	—	Target height in pixels (1-32768).
`output`	string	—	base64 (default): inline. url: stored for 24 hours; link, metadata.
`quality`	object	—	Encoder quality 1-100 (lossy formats).
`upscale`	boolean	—	Allow output larger than the input.
`lossless`	boolean	—	webp output: lossless encoding (default false).
`optimize`	boolean	—	png output: maximum (slower) compression (default false).
`resample`	string	—	Resampling filter: nearest, box, bilinear, hamming, bicubic or lanczos (default).

Parameters from the server's own tool schema.

RISK

Why image_resize is rated Medium

An AI agent can call image_resize faster than any human can review: one bad instruction and it creates or modifies resources in Tanod by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (url) · High parameter count (16 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs image_resize safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For image_resize, this is the rule to start with:

image_resize Rate-limited

image_resize 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "image_resize": {
      "limits": [
        {
          "counter": "image_resize_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every image_resize call is checked against it from then on.

FAQ

Questions about image_resize

What does the image_resize tool do? +

imagepeek: Resize an image. For several sizes in one call use image_thumbnail; for a box or ratio use image_crop. Returns the image resized to width and/or height (or by scale) with fit inside (default), contain (letterboxed on background), cover (centre crop) or fill (stretched), Lanczos by default; never upscaled unless upscale is true (then upscale_prevented says so). Reads PNG, JPEG, WebP, GIF, TIFF, BMP, ICO and AVIF; other formats and images over 40 megapixels are refused (not charged). Output: base64 data_base64, without EXIF, GPS, XMP or IPTC; over 15 MB or 50 megapixels is a 413 (not charged). Images are not logged; a result is kept only with output "url" (24 h). Typically 0.5-2 s. Price: USD 0.002. Free: 3 imagepeek calls per IP per UTC day. Docs: https://tanod.dev/learn/image-resize-api.html. It is categorised as a Write tool in the Tanod MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does image_resize accept? +

image_resize accepts 12 parameters: fit, url, scale, width, format, height, output, quality, upscale, lossless, optimize, resample. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on image_resize? +

Register the Tanod MCP server in PolicyLayer and add a rule for image_resize: 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 Tanod. Nothing to install.

What risk level is image_resize? +

image_resize is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit image_resize? +

Yes. Add a rate_limit block to the image_resize 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.

How do I block image_resize completely? +

Set action: deny in the PolicyLayer policy for image_resize. 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 image_resize? +

image_resize is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tanod, and thousands of servers like it.

This server

All 308 Tanod tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →