Medium Risk

image_to_image

Generate an image from an existing image using WaveSpeed AI.

How to control image_to_image ↓

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

Medium Risk

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

Documented attack patterns abuse exactly the kind of access image_to_image gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and WavespeedMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for image_to_image:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "image_to_image": {
      "limits": [
        {
          "counter": "image_to_image_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register WavespeedMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the image_to_image tool do? +

Generate an image from an existing image using WaveSpeed AI. It is categorised as a Write tool in the WavespeedMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on image_to_image? +

Register the Wavespeed MCP server in PolicyLayer and add a rule for image_to_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 WavespeedMCP. Nothing to install.

What risk level is image_to_image? +

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

Can I rate-limit image_to_image? +

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

How do I block image_to_image completely? +

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

What MCP server provides image_to_image? +

image_to_image is provided by the Wavespeed MCP server (wavespeedai/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WavespeedMCP tool call.

Deterministic rules across all 3 WavespeedMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

3 WavespeedMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.