Upload an image to Runware by providing a file path on the local file system or publicurl. This function reads the image file directly from the file path or public url and uploads it to Runware. It returns a Runware UUID that can be used in other tools that require image inputs....
Accepts file system path (file_path)
Part of the Mcp Runware MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use imageUpload to create or modify resources in Mcp Runware. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call imageUpload repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Runware.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
imageUpload:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Mcp Runware policy for all 11 tools.
Agents calling write-class tools like imageUpload have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Upload an image to Runware by providing a file path on the local file system or publicurl. This function reads the image file directly from the file path or public url and uploads it to Runware. It returns a Runware UUID that can be used in other tools that require image inputs. IMPORTANT: This tool should be used FIRST when you need to process local images with other Runware tools. The returned UUID can then be used as input for tools like imageInference, photoMaker, imageUpscale, etc. Workflow: 1. Use this tool to upload a local image and get a Runware UUID 2. Use the returned UUID in other Runware tools that require image inputs 3. This prevents context pollution and ensures proper image handling Args: file_path (str): Path to the image file on the local file system Examples: "/path/to/image.jpg", "images/photo.png", "./uploads/file.webp" Supported formats: PNG, JPG, WEBP, JPEG, BMP, GIF Returns: dict: A dictionary containing the upload result with status, message, result data, and the uploaded image UUID for future reference. Note: - Images are deleted 30 days after last use, but remain available indefinitely while in use - File path must be accessible - Use the returned UUID in other Runware tools instead of file paths or base64 data . It is categorised as a Write tool in the Mcp Runware MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for imageUpload. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Runware MCP server.
imageUpload 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 imageUpload rule in your Intercept 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 Intercept policy for imageUpload. 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.
imageUpload is provided by the Mcp Runware MCP server (elijahdev0/mcp-runware). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept