New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

image_blurhash

imagepeek: Generate a BlurHash placeholder string for an image. For the palette use image_colors. Returns the BlurHash string of an image (the published woltapp algorithm, identical to the reference package), with x_components and y_components 1-9 (default 4 x 3), for blurred placeholders while t...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Low RISK CLASS
Category Read
Parameters 50 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What image_blurhash does on Tanod

AI agents call image_blurhash to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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.
auto_orient boolean — Apply the EXIF orientation first (default true).
image_base64 object — The image as standard or url-safe base64 (at most 10 MB decoded; a data:image/...;base64, prefix is fine); or use url.
x_components integer — Horizontal components (1-9, default 4): more detail, a longer hash.
y_components integer — Vertical components (1-9, default 3).

Parameters from the server's own tool schema.

Why image_blurhash is rated Low

Even though image_blurhash only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts URL/endpoint input (url)

Questions about image_blurhash

What does the image_blurhash tool do? +

imagepeek: Generate a BlurHash placeholder string for an image. For the palette use image_colors. Returns the BlurHash string of an image (the published woltapp algorithm, identical to the reference package), with x_components and y_components 1-9 (default 4 x 3), for blurred placeholders while the real image loads. Reads PNG, JPEG, WebP, GIF, TIFF, BMP, ICO and AVIF; other formats and images over 40 megapixels are refused (not charged). Images are never logged or stored. Typically 0.5-2 s. Price: USD 0.002. Free: 3 imagepeek calls per IP per UTC day. Docs: https://tanod.dev/learn/blurhash-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.

What parameters does image_blurhash accept? +

image_blurhash accepts 5 parameters: url, auto_orient, image_base64, x_components, y_components. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on image_blurhash? +

Register the Tanod MCP server in PolicyLayer and add a rule for image_blurhash: 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_blurhash? +

image_blurhash is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit image_blurhash? +

Yes. Add a rate_limit block to the image_blurhash 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_blurhash completely? +

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

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

More on Tanod, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tanod's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.