Delete an OpenAI assistant
AI agents call delete-assistant to permanently remove resources in OpenAI Assistant MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an assistant is an irreversible action that removes a resource and its associated configuration. This cannot be undone without recreating the assistant from scratch. While not involving financial transactions or data exfiltration, the permanent removal of a managed resource represents a destructive capability.
From the tool's definition Tool name is 'delete-assistant' and description states 'Delete an OpenAI assistant'. The verb 'delete' combined with the irreversible nature of removing an assistant configuration indicates a destructive operation.
Attacks that exploit this kind of access
Delete an OpenAI assistant. It is categorised as a Destructive tool in the OpenAI Assistant MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenAI Assistant MCP Server MCP server in PolicyLayer and add a rule for delete-assistant: 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 OpenAI Assistant MCP Server. Nothing to install.
delete-assistant 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-assistant 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-assistant. 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-assistant is provided by the OpenAI Assistant MCP Server MCP server (snilld-ai/openai-assistant-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 →