kicad_gui_click_atspi

Backend B: activate the first accessible node matching

SERVERKiCAD-MCP-Server SOURCEmixelpixx/kicad-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/kicad-gui-click-atspi.md

WHAT IT DOES

What kicad_gui_click_atspi does on KiCAD-MCP-Server

AI agents invoke kicad_gui_click_atspi to trigger actions in KiCAD-MCP-Server. 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.

RISK

Why kicad_gui_click_atspi is rated High

Activates GUI elements programmatically, triggering external UI operations with unpredictable effects.

From the tool's definition activate the first accessible node matching

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs kicad_gui_click_atspi safely

PolicyLayer is an MCP gateway: it sits between your AI agents and KiCAD-MCP-Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kicad_gui_click_atspi, this is the rule to start with:

kicad_gui_click_atspi Rate-limited

kicad_gui_click_atspi 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": {
    "kicad_gui_click_atspi": {
      "limits": [
        {
          "counter": "kicad_gui_click_atspi_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every kicad_gui_click_atspi call is checked against it from then on.

FAQ

Questions about kicad_gui_click_atspi

What does the kicad_gui_click_atspi tool do? +

Backend B: activate the first accessible node matching. It is categorised as a Execute tool in the KiCAD-MCP-Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kicad_gui_click_atspi? +

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

What risk level is kicad_gui_click_atspi? +

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

Can I rate-limit kicad_gui_click_atspi? +

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

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

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

KEEP EXPLORING

More on KiCAD-MCP-Server, and thousands of servers like it.

This server

All 247 KiCAD-MCP-Server tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →