delete_image
Delete one of your uploaded images by id. Removes the stored file and frees the storage it used. Only your own images can be deleted.
This record as markdown: /tools/flowdot-llc-mcp-server/delete-image.md
What delete_image does on FlowDot MCP Server
AI agents call delete_image to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_image is rated Critical
This tool permanently deletes user-uploaded image files and cannot be undone. While scoped to the user's own images (mitigating some risk), the irreversible nature of file deletion and the potential for unintended data loss if an AI agent misuses the image ID parameter classifies this as Destructive rather than Write.
From the tool's definition Tool description explicitly states 'Delete one of your uploaded images by id' and 'Removes the stored file and frees the storage it used.' The verb 'Delete' combined with 'Removes the stored file' indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_image, this is the rule to start with:
delete_image is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every delete_image call is checked against it from then on.
Questions about delete_image
Delete one of your uploaded images by id. Removes the stored file and frees the storage it used. Only your own images can be deleted. It is categorised as a Destructive tool in the FlowDot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_image is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue