image-generation.edit

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

Medium RISK CLASS

Category Write

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/image-generation.edit.md

WHAT IT DOES

What image-generation.edit does on Vee3

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

Parameter	Type	Required	Description
`n`	integer	—	Number of images to generate (1 to 10). Each returned image costs 50 tokens.
`size`	object	—	Optional output size as WIDTHxHEIGHT (for example 1024x1536) or auto. This sets aspect ratio, not exact pixel size. Omit for the default aspect ratio.
`images`	array	Yes	Source images as stored file names from files.list_uploaded_files and/or public http or https image URLs. One image is an edit. Several images are composed into
`prompt`	string	Yes	Text description of the image to generate or of the edit to apply.
`file_name`	object	—	Optional account-relative storage path for the image. When n is greater than 1, an index is inserted before the extension (for example art/fox.webp becomes art/
`output_format`	string	—	Encoding of the returned image. webp is smaller; png is lossless.

Parameters from the server's own tool schema.

RISK

Why image-generation.edit is rated Medium

Creates or modifies images and saves results to storage; reversible write action.

From the tool's definition Edit an existing image or compose several images into one scene

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs image-generation.edit safely

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

image-generation.edit Rate-limited

image-generation.edit 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-generation.edit": {
      "limits": [
        {
          "counter": "image-generation.edit_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 Vee3, apply this rule, and every image-generation.edit call is checked against it from then on.

FAQ

Questions about image-generation.edit

What does the image-generation.edit tool do? +

Edit an existing image or compose several images into one scene with Muse Image. The user or agent passes stored file names from files.list_uploaded_files and/or public http or https image URLs. One image is an edit; several images are composed into one result. The result is saved to account file storage. The response includes a signed URL for API users and download_code for agents to run vee3-get-file. Cost = 50 tokens per generated image. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does image-generation.edit accept? +

image-generation.edit accepts 6 parameters: n, size, images, prompt, file_name, output_format. Required: images, prompt. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on image-generation.edit? +

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

What risk level is image-generation.edit? +

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

Can I rate-limit image-generation.edit? +

Yes. Add a rate_limit block to the image-generation.edit 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-generation.edit completely? +

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

image-generation.edit is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 269 Vee3 tools →

Across the catalogue

The MCP Attack Database →

Guides

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