Check the installation status of Qiskit Metal and dependencies
AI agents call check_qiskit_installation to retrieve information from Funky Junction without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check of installation status. It queries the state of installed packages and their dependencies but does not install, modify, delete, or execute any code. It has no side effects and presents minimal risk even if misused—the worst outcome would be retrieving installation information. This clearly fits the Read category with low severity.
From the tool's definition Tool name 'check_qiskit_installation' and description 'Check the installation status of Qiskit Metal and dependencies' indicate a query/inspection operation that retrieves status information without modifying any system state or executing arbitrary code.
Attacks that exploit this kind of access
Check the installation status of Qiskit Metal and dependencies. It is categorised as a Read tool in the Funky Junction MCP Server, which means it retrieves data without modifying state.
Register the Funky Junction MCP server in PolicyLayer and add a rule for check_qiskit_installation: 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 Funky Junction. Nothing to install.
check_qiskit_installation 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 check_qiskit_installation 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 check_qiskit_installation. 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.
check_qiskit_installation is provided by the Funky Junction MCP server (paulgoldschmidt/qsim-mcp). 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 →