High Risk →

run_estimator_tool

run_estimator_tool

How to control run_estimator_tool ↓

AI agents invoke run_estimator_tool to trigger actions in Qiskit Code Assistant MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

run_estimator_tool triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Documented attack patterns abuse exactly the kind of access run_estimator_tool gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Qiskit Code Assistant MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_estimator_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_estimator_tool": {
      "limits": [
        {
          "counter": "run_estimator_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

run_estimator_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Qiskit Code Assistant MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the run_estimator_tool tool do? +

run_estimator_tool. It is categorised as a Execute tool in the Qiskit Code Assistant MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_estimator_tool? +

Register the Qiskit Code Assistant MCP Server MCP server in PolicyLayer and add a rule for run_estimator_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 Code Assistant MCP Server. Nothing to install.

What risk level is run_estimator_tool? +

run_estimator_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_estimator_tool? +

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

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

run_estimator_tool is provided by the Qiskit Code Assistant MCP Server MCP server (qiskit-code-assistant-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 Code Assistant MCP Server tool call.

Deterministic rules across all 71 Qiskit Code Assistant MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

71 Qiskit Code Assistant MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.