blur
A write tool on the πͺ ImageSorcery MCP server.
This record as markdown: /tools/sunriseapps-imagesorcery-mcp/blur.md
What blur does on πͺ ImageSorcery MCP
AI agents use blur to create or update resources in πͺ ImageSorcery MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your πͺ ImageSorcery MCP environment.
Why blur is rated Medium
Based on the tool name 'blur' and the context of an image manipulation MCP server (ImageSorcery) with sibling tools like crop, draw, fill, and change_color, this tool most likely applies a blur effect to an image, which is a reversible modification (Write). However, confidence is reduced due to the empty description β it could potentially overwrite the original file destructively.
From the tool's definition Tool name is 'blur'; description is empty or uninformative.
Attacks that exploit this kind of access
The rule that runs blur safely
PolicyLayer is an MCP gateway: it sits between your AI agents and πͺ ImageSorcery MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blur, this is the rule to start with:
blur 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 πͺ ImageSorcery MCP, apply this rule, and every blur call is checked against it from then on.
Questions about blur
blur is a write tool on the πͺ ImageSorcery MCP server. It is categorised as a Write tool in the πͺ ImageSorcery MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the πͺ ImageSorcery MCP server in PolicyLayer and add a rule for blur: 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 πͺ ImageSorcery MCP. Nothing to install.
blur 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 blur 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 blur. 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.
blur is provided by the πͺ ImageSorcery MCP server (sunriseapps/imagesorcery-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on πͺ ImageSorcery, and thousands of servers like it.
This server
Across the catalogue