delete_style
Delete a style (e.g. a failed analysis experiment). Don't delete a style that projects still use as their default — rebind them first with set_project_style.
This record as markdown: /tools/com-framesail-framesail/delete-style.md
What delete_style does on Framesail
AI agents call delete_style to permanently remove resources in Framesail, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
style_id | string | Yes | ID of the style to delete, from list_styles |
Parameters from the server's own tool schema.
Why delete_style is rated Critical
This tool irreversibly deletes style data from the system. While the blast radius is contained to style definitions (not user-facing content directly), deletion of a style could break projects that depend on it if precautions aren't followed. The instruction to rebind projects first acknowledges the destructive nature.
From the tool's definition Tool name 'delete_style' and description explicitly states 'Delete a style' which is an irreversible deletion operation. The warning to avoid deleting styles in use indicates this action cannot be easily undone and could break project configurations.
Attacks that exploit this kind of access
The rule that runs delete_style safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_style, this is the rule to start with:
delete_style 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 Framesail, apply this rule, and every delete_style call is checked against it from then on.
Questions about delete_style
Delete a style (e.g. a failed analysis experiment). Don't delete a style that projects still use as their default — rebind them first with set_project_style. It is categorised as a Destructive tool in the Framesail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_style accepts 1 parameter: style_id. Required: style_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for delete_style: 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 Framesail. Nothing to install.
delete_style 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_style 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_style. 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_style is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
Across the catalogue