Delete an image generation preset. This is IRREVERSIBLE.
AI agents call delete_image_generation_preset to permanently remove resources in DMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a stored image generation preset configuration. Although the blast radius is limited to game assets rather than critical data, the irreversible nature of deletion and the explicit warning about irreversibility classify this as Destructive.
From the tool's definition The description explicitly states 'Delete an image generation preset. This is IRREVERSIBLE.' The tool name contains 'delete' and the description confirms the action cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_image_generation_preset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_image_generation_preset:
{
"version": "1",
"default": "deny",
"hide": [
"delete_image_generation_preset"
]
} delete_image_generation_preset disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an image generation preset. This is IRREVERSIBLE. It is categorised as a Destructive tool in the DMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the D MCP server in PolicyLayer and add a rule for delete_image_generation_preset: 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 DMCP. Nothing to install.
delete_image_generation_preset 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_generation_preset 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_generation_preset. 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_generation_preset is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.