load_circuit_from_qasm_tool
AI agents call load_circuit_from_qasm_tool to retrieve information from Qiskit Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The function loads and parses a QASM (Quantum Assembly) circuit definition into memory—a read-only data deserialization operation. There are no side effects (no modification, deletion, or execution of the circuit itself). Despite the empty description reducing confidence, the name strongly suggests a retrieval/parsing operation typical of the Read category.
From the tool's definition Tool name 'load_circuit_from_qasm_tool' indicates parsing/loading a circuit from OpenQASM format. No description provided, which lowers confidence.
Attacks that exploit this kind of access
load_circuit_from_qasm_tool. It is categorised as a Read tool in the Qiskit Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qiskit Documentation MCP Server MCP server in PolicyLayer and add a rule for load_circuit_from_qasm_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.
load_circuit_from_qasm_tool is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the load_circuit_from_qasm_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 load_circuit_from_qasm_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.
load_circuit_from_qasm_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 →