run_sampler_tool
A execute tool on the Qiskit IBM Transpiler MCP server.
This record as markdown: /tools/qiskit-ibm-transpiler-mcp-server/run-sampler-tool.md
What run_sampler_tool does on Qiskit IBM Transpiler MCP Server
AI agents invoke run_sampler_tool to trigger actions in Qiskit IBM Transpiler 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.
Why run_sampler_tool is rated High
Sampling tools in quantum computing frameworks execute quantum circuits on simulators or real hardware. This is an Execute category because it triggers external operations (quantum sampling) with effects determined by the provided arguments (circuits, shots, parameters). While not immediately destructive to classical data, it commits computational resources and can produce side effects dependent on untrusted input.
From the tool's definition Tool name 'run_sampler_tool' in the Qiskit IBM Transpiler MCP Server context indicates execution of quantum sampling operations.
Attacks that exploit this kind of access
The rule that runs run_sampler_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 run_sampler_tool, this is the rule to start with:
run_sampler_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Qiskit IBM Transpiler MCP Server, apply this rule, and every run_sampler_tool call is checked against it from then on.
Questions about run_sampler_tool
run_sampler_tool is a execute tool on the Qiskit IBM Transpiler MCP Server MCP server. It is categorised as a Execute tool in the Qiskit IBM Transpiler MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qiskit IBM Transpiler MCP Server MCP server in PolicyLayer and add a rule for run_sampler_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.
run_sampler_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_sampler_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 run_sampler_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.
run_sampler_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.
Across the catalogue