Install Qiskit Metal and required dependencies
AI agents invoke install_qiskit_dependencies to trigger actions in Funky Junction. 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.
Installing software dependencies executes system-level package management commands (e.g., pip install) that modify the host environment. This is an Execute-category action with high severity because an AI agent misusing it could install malicious or incorrect packages, alter system state, introduce version conflicts, or compromise the runtime environment.
From the tool's definition "Install Qiskit Metal and required dependencies" — installs software packages onto the host system
Attacks that exploit this kind of access
Install Qiskit Metal and required dependencies. It is categorised as a Execute tool in the Funky Junction MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Funky Junction MCP server in PolicyLayer and add a rule for install_qiskit_dependencies: 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.
install_qiskit_dependencies 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 install_qiskit_dependencies 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 install_qiskit_dependencies. 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.
install_qiskit_dependencies 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 →