upload_image
Upload an image (bare base64) to your FlowDot storage bucket and get back a public direct URL you can embed anywhere (e.g. a toolkit README). The image is persisted to your account and counts toward your storage quota. Raster formats only: image/png, image/jpeg, image/webp. SVG is NOT accepted — ...
This record as markdown: /tools/flowdot-llc-mcp-server/upload-image.md
What upload_image does on FlowDot MCP Server
AI agents use upload_image to create or update resources in FlowDot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlowDot MCP Server environment.
Why upload_image is rated Medium
The tool creates new persistent data (image files stored in account storage) and modifies account state (storage quota consumption). This is a Write-category operation because it stores data reversibly without deleting or irreversibly overwriting existing content.
From the tool's definition Tool performs file upload and storage operations that create/persist data: 'Upload an image... The image is persisted to your account and counts toward your storage quota.' This is a reversible modification of account storage state.
Attacks that exploit this kind of access
The rule that runs upload_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_image, this is the rule to start with:
upload_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.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every upload_image call is checked against it from then on.
Questions about upload_image
Upload an image (bare base64) to your FlowDot storage bucket and get back a public direct URL you can embed anywhere (e.g. a toolkit README). The image is persisted to your account and counts toward your storage quota. Raster formats only: image/png, image/jpeg, image/webp. SVG is NOT accepted — rasterize vector art to PNG first (e.g. with the image tools svg_to_png). It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for upload_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 FlowDot MCP Server. Nothing to install.
upload_image 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 upload_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.
Set action: deny in the PolicyLayer policy for upload_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.
upload_image is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue