add_qubit · Funky Junction MCP: Risk & Policy

WHAT IT DOES

What add_qubit does on Funky Junction

AI agents use add_qubit to create or update resources in Funky Junction — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Funky Junction environment.

WHY IT NEEDS A POLICY

Why add_qubit needs a policy

This tool creates a new qubit object within the circuit design model, which is a reversible modification of the design state. It does not execute simulations, delete components, move financial resources, or run arbitrary external code—it simply instantiates a new circuit component that can be modified or removed later.

From the tool's definition add_qubit: 'Add a new superconducting qubit to the system' — the verb 'Add' indicates creation of a new component in the quantum circuit design system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_qubit Rate-limited

add_qubit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_qubit": {
      "limits": [
        {
          "counter": "add_qubit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Funky Junction, so you can run agents against it safely.

FAQ

Questions about add_qubit

What does the add_qubit tool do? +

Add a new superconducting qubit to the system. It is categorised as a Write tool in the Funky Junction MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_qubit? +

Register the Funky Junction MCP server in PolicyLayer and add a rule for add_qubit: 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.

What risk level is add_qubit? +

add_qubit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_qubit? +

Yes. Add a rate_limit block to the add_qubit 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.

How do I block add_qubit completely? +

Set action: deny in the PolicyLayer policy for add_qubit. 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.

What MCP server provides add_qubit? +

add_qubit 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.