Low Risk

total_instances

Count of available instances

Part of the Qiskit IBM Runtime MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call total_instances to retrieve information from Qiskit IBM Runtime MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though total_instances only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

qiskit-ibm-runtime-mcp-server.yaml
tools:
  total_instances:
    rules:
      - action: allow

See the full Qiskit IBM Runtime MCP Server policy for all 62 tools.

Tool Name total_instances
Category Read
Risk Level Low

View all 62 tools →

Agents calling read-class tools like total_instances have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the total_instances tool do? +

Count of available instances. It is categorised as a Read tool in the Qiskit IBM Runtime MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on total_instances? +

Add a rule in your Intercept YAML policy under the tools section for total_instances. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Qiskit IBM Runtime MCP Server MCP server.

What risk level is total_instances? +

total_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit total_instances? +

Yes. Add a rate_limit block to the total_instances rule in your Intercept 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 total_instances completely? +

Set action: deny in the Intercept policy for total_instances. 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 total_instances? +

total_instances is provided by the Qiskit IBM Runtime MCP Server MCP server (qiskit-ibm-runtime-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Qiskit IBM Runtime MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.