auto_place_decoupling_cap · Kicad MCP: Risk & Policy

WHAT IT DOES

What auto_place_decoupling_cap does on Kicad

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

WHY IT NEEDS A POLICY

Why auto_place_decoupling_cap needs a policy

This tool automatically places decoupling capacitors in a KiCad project, which modifies the design by adding components to the schematic or PCB. This is reversible (components can be removed) so it falls under Write rather than Destructive. Severity is high because misplaced decoupling capacitors could compromise circuit functionality, create design errors, or require significant rework.

From the tool's definition Tool name contains 'auto_place' and operates in KiCad design context; sibling tools (add_copper_zone, add_pcb_line, add_label, etc.) are all component-adding/modification operations. The 'auto_' prefix suggests automated modification of PCB/schematic layout.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auto_place_decoupling_cap Rate-limited

auto_place_decoupling_cap 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": {
    "auto_place_decoupling_cap": {
      "limits": [
        {
          "counter": "auto_place_decoupling_cap_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 Kicad, so you can run agents against it safely.

FAQ

Questions about auto_place_decoupling_cap

What does the auto_place_decoupling_cap tool do? +

auto_place_decoupling_cap. It is categorised as a Write tool in the Kicad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on auto_place_decoupling_cap? +

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

What risk level is auto_place_decoupling_cap? +

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

Can I rate-limit auto_place_decoupling_cap? +

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

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

auto_place_decoupling_cap is provided by the Kicad MCP server (productofamerica/mcp-server-kicad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.