Add a Josephson junction using the Manhattan model.
AI agents use add_josephson_junction 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.
The tool adds (creates) a Josephson junction to a quantum circuit design, which is a reversible modification of the design artifact. This is a Write operation—it changes the circuit structure but does not execute simulations, delete data, or trigger external operations.
From the tool's definition Tool name 'add_josephson_junction' and description 'Add a Josephson junction using the Manhattan model' indicate creation of a circuit component within a quantum design system.
Attacks that exploit this kind of access
Add a Josephson junction using the Manhattan model. 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_josephson_junction: 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_josephson_junction 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_josephson_junction 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_josephson_junction. 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_josephson_junction 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 →