connect_components · Funky Junction MCP: Risk & Policy

WHAT IT DOES

What connect_components does on Funky Junction

AI agents use connect_components 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 connect_components needs a policy

The tool creates or modifies circuit design by connecting quantum circuit components. This is a Write operation because it alters the circuit design state reversibly. Severity is medium because misuse could corrupt a circuit design workflow, but the effects are contained to the design artifact and reversible.

From the tool's definition Tool named 'connect_components' in a quantum circuit design context (Qiskit Metal). Sibling tools include add_qubit, add_cpw_waveguide, add_josephson_junction, indicating the server manages circuit topology.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_components Rate-limited

connect_components 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": {
    "connect_components": {
      "limits": [
        {
          "counter": "connect_components_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 connect_components

What does the connect_components tool do? +

connect_components. 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 connect_components? +

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

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

Can I rate-limit connect_components? +

Yes. Add a rate_limit block to the connect_components 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 connect_components completely? +

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

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