available_instances_tool
A read tool on the Qiskit IBM Transpiler MCP server.
This record as markdown: /tools/qiskit-ibm-transpiler-mcp-server/available-instances-tool.md
What available_instances_tool does on Qiskit IBM Transpiler MCP Server
AI agents call available_instances_tool to retrieve information from Qiskit IBM Transpiler MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why available_instances_tool is rated Low
This tool retrieves information about available Qiskit instances without modifying any state. It is a standard inventory/discovery query operation with no side effects or capability to alter data, execute operations, or commit resources. Low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'available_instances_tool' strongly suggests listing or retrieving available instances. Sibling tools like 'active_instance_info_tool' and 'active_account_info_tool' further indicate this is a read-only querying tool.
Attacks that exploit this kind of access
The rule that runs available_instances_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Qiskit IBM Transpiler MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For available_instances_tool, this is the rule to start with:
available_instances_tool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Qiskit IBM Transpiler MCP Server, apply this rule, and every available_instances_tool call is checked against it from then on.
Questions about available_instances_tool
available_instances_tool is a read tool on the Qiskit IBM Transpiler MCP Server MCP server. It is categorised as a Read tool in the Qiskit IBM Transpiler MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qiskit IBM Transpiler MCP Server MCP server in PolicyLayer and add a rule for available_instances_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.
available_instances_tool is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the available_instances_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 available_instances_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.
available_instances_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.
This server
Across the catalogue