delete_saved_account_tool

delete_saved_account_tool

Server Qiskit Documentation MCP Server pypi:qiskit-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_saved_account_tool does on Qiskit Documentation MCP Server

AI agents call delete_saved_account_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.

Why delete_saved_account_tool needs a policy

The 'delete' operation is inherently destructive and cannot be undone. Removing saved account credentials or configurations could disrupt authentication workflows, break integrations, or require manual reconfiguration. Despite the empty description limiting full context, the explicit 'delete' verb combined with account management context places this in the Destructive category (more severe than Write).

From the tool's definition Tool name is 'delete_saved_account_tool' with empty description. The verb 'delete' combined with 'saved_account' indicates irreversible removal of account configuration data.

Questions about delete_saved_account_tool

What does the delete_saved_account_tool tool do? +

delete_saved_account_tool. 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.

How do I enforce a policy on delete_saved_account_tool? +

Register the Qiskit Documentation MCP Server MCP server in PolicyLayer and add a rule for delete_saved_account_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.

What risk level is delete_saved_account_tool? +

delete_saved_account_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_saved_account_tool? +

Yes. Add a rate_limit block to the delete_saved_account_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_saved_account_tool completely? +

Set action: deny in the PolicyLayer policy for delete_saved_account_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_saved_account_tool? +

delete_saved_account_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.