Low Risk

original_circuit

View metrics for the input circuit

Part of the Qiskit IBM Transpiler MCP Server server.

original_circuit is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE QISKIT IBM TRANSPILER MCP SERVER →

Free to start. No card required.

AI agents call original_circuit to retrieve information from Qiskit IBM Transpiler 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 original_circuit 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "original_circuit": {}
  }
}

See the full Qiskit IBM Transpiler MCP Server policy for all 8 tools.

Get this rule live on your own Qiskit IBM Transpiler MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY QISKIT IBM TRANSPILER MCP SERVER →

These attack patterns abuse exactly the kind of access original_circuit gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so original_circuit only ever does what you allow.

SECURE QISKIT IBM TRANSPILER MCP SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the original_circuit tool do? +

View metrics for the input circuit. It is categorised as a Read tool in the Qiskit IBM Transpiler MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on original_circuit? +

Register the Qiskit IBM Transpiler MCP Server MCP server in PolicyLayer and add a rule for original_circuit: 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.

What risk level is original_circuit? +

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

Can I rate-limit original_circuit? +

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

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

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

Enforce policy on every Qiskit IBM Transpiler MCP Server tool call.

Deterministic rules across all 8 Qiskit IBM Transpiler 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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.