Delete a user preset.
AI agents call delete_preset to permanently remove resources in QIDI Studio MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes user-created preset configurations. Deletion operations that cannot be recovered are classified as Destructive rather than Write. Given the potential for an AI agent to inadvertently delete important or critical printing profiles that users depend on, the severity is high. Confidence is high because the name and description unambiguously indicate a delete operation.
From the tool's definition Tool name is 'delete_preset' and description states 'Delete a user preset.' The verb 'delete' combined with the irreversible nature of removing a preset configuration indicates a destructive action that cannot be undone.
Attacks that exploit this kind of access
Delete a user preset. It is categorised as a Destructive tool in the QIDI Studio MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QIDI Studio MCP Server MCP server in PolicyLayer and add a rule for delete_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 QIDI Studio MCP Server. Nothing to install.
delete_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_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_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_preset is provided by the QIDI Studio MCP Server MCP server (vladyankovenko/qidi-studio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →