run_sampler_tool
AI agents invoke run_sampler_tool to trigger actions in Qiskit Documentation 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.
A sampler tool in quantum computing contexts executes quantum circuits and returns measurement results—this is definitionally an Execute action that triggers external operations (sampling from quantum hardware or simulators) whose effects depend on the circuit arguments provided.
From the tool's definition Tool name 'run_sampler_tool' indicates execution of a quantum sampler, which triggers external quantum computing operations.
Attacks that exploit this kind of access
run_sampler_tool. It is categorised as a Execute tool in the Qiskit Documentation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qiskit Documentation 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 Documentation 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 Documentation MCP Server MCP server (pypi:qiskit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →