Delete a model.
AI agents call delete_model_tool to permanently remove resources in Qiskit Documentation MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs a destructive operation that permanently removes a model without the ability to undo the action. Although the Qiskit server context suggests this operates on quantum computing models/circuits rather than critical production data, deletion is inherently irreversible and ranks higher than Execute or Write categories.
From the tool's definition Tool name 'delete_model_tool' with description 'Delete a model' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete a model. It is categorised as a Destructive tool in the Qiskit Documentation MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Qiskit Documentation 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 Documentation MCP Server. Nothing to install.
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.
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.
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.
delete_model_tool is provided by the Qiskit Documentation MCP Server MCP server (pypi:qiskit-mcp-server). 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 →