Delete a saved IBM Quantum account
Risk signalsPermanently removes saved account credentials
Part of the Qiskit IBM Runtime MCP Server server.
Free to start. No card required.
AI agents may call account_name to permanently remove or destroy resources in Qiskit IBM Runtime MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call account_name in a loop, permanently destroying resources in Qiskit IBM Runtime MCP Server. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"account_name"
]
}See the full Qiskit IBM Runtime MCP Server policy for all 62 tools.
These attack patterns abuse exactly the kind of access account_name gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Delete a saved IBM Quantum account. It is categorised as a Destructive tool in the Qiskit IBM Runtime MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Qiskit IBM Runtime MCP Server MCP server in PolicyLayer and add a rule for account_name: 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 Runtime MCP Server. Nothing to install.
account_name 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 account_name 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 account_name. 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.
account_name is provided by the Qiskit IBM Runtime MCP Server MCP server (qiskit-ibm-runtime-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 62 Qiskit IBM Runtime MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.