openems_create_via · Mcp Openems MCP: Risk & Policy

WHAT IT DOES

What openems_create_via does on Mcp Openems

AI agents invoke openems_create_via to trigger actions in Mcp Openems. 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.

WHY IT NEEDS A POLICY

Why openems_create_via needs a policy

This tool generates and runs an FDTD simulation model (full-wave script generation) for a PCB via transition. It executes simulation workflows and produces geometry/analysis outputs. While it involves 'creating' a design, the core action is executing a simulation/script generation process rather than simply writing persistent data, consistent with the server's description of 'full-wave script generation'.

From the tool's definition Design a via transition... Models via barrel, pads, and feed traces... 2-port geometry for reflection/transmission analysis

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

openems_create_via Rate-limited

openems_create_via stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "openems_create_via": {
      "limits": [
        {
          "counter": "openems_create_via_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about openems_create_via

What does the openems_create_via tool do? +

Design a via transition between two PCB layers. Models via barrel, pads, and feed traces. Estimates parasitic inductance and capacitance. 2-port geometry for reflection/transmission analysis. It is categorised as a Execute tool in the Mcp Openems MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on openems_create_via? +

Register the Mcp Openems MCP server in PolicyLayer and add a rule for openems_create_via: 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 Mcp Openems. Nothing to install.

What risk level is openems_create_via? +

openems_create_via is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit openems_create_via? +

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

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

openems_create_via is provided by the Mcp Openems MCP server (rfingadam/mcp-openems). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.