Add a square spiral coupler between Q1 and Q2.
AI agents use add_coupler 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.
This tool creates or modifies a quantum circuit design by adding a coupler element between two qubits. This is a reversible design operation (components can be removed or modified) with no side effects beyond the local circuit model. It does not execute simulations, delete data, or trigger external operations—it merely updates the circuit design state.
From the tool's definition add_coupler: Add a square spiral coupler between Q1 and Q2. The verb 'Add' indicates creation of a new design component within the quantum circuit.
Attacks that exploit this kind of access
Add a square spiral coupler between Q1 and Q2. 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.
Register the Funky Junction MCP server in PolicyLayer and add a rule for add_coupler: 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.
add_coupler is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_coupler 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 add_coupler. 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.
add_coupler 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 →