New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_model_tool

Delete a model.

SERVERQiskit IBM Transpiler MCP Server SOURCEqiskit-ibm-transpiler-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/qiskit-ibm-transpiler-mcp-server/delete-model-tool.md

What delete_model_tool does on Qiskit IBM Transpiler MCP Server

AI agents call delete_model_tool to permanently remove resources in Qiskit IBM Transpiler MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_model_tool is rated Critical

The tool performs an irreversible delete operation on a model object. While the context (Qiskit IBM Transpiler) suggests this operates on quantum transpilation models rather than financial or safety-critical systems, deletion is inherently destructive and cannot be undone. An AI agent misusing this tool could permanently remove trained models, research work, or configurations.

From the tool's definition Tool name 'delete_model_tool' with description 'Delete a model.' explicitly indicates irreversible deletion of data.

Questions about delete_model_tool

What does the delete_model_tool tool do? +

Delete a model. It is categorised as a Destructive tool in the Qiskit IBM Transpiler MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_model_tool? +

Register the Qiskit IBM Transpiler MCP Server MCP server in PolicyLayer and add a rule for delete_model_tool: 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 Qiskit IBM Transpiler MCP Server. Nothing to install.

What risk level is delete_model_tool? +

delete_model_tool is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_model_tool? +

Yes. Add a rate_limit block to the delete_model_tool 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.

How do I block delete_model_tool completely? +

Set action: deny in the PolicyLayer policy for delete_model_tool. 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.

What MCP server provides delete_model_tool? +

delete_model_tool is provided by the Qiskit IBM Transpiler MCP Server MCP server (qiskit-ibm-transpiler-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Qiskit IBM Transpiler MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Qiskit IBM Transpiler MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.