check_kicad_ui

Check if KiCAD UI is currently running

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/check-kicad-ui.md

WHAT IT DOES

What check_kicad_ui does on KiCAD-MCP-Server

AI agents call check_kicad_ui to retrieve information from KiCAD-MCP-Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_kicad_ui is rated Low

This tool only checks the state of a running application (whether KiCAD UI is active). It performs a read-only operation that retrieves information about the current system state without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent could only determine if KiCAD is running, which has no harmful consequences.

From the tool's definition Tool name 'check_kicad_ui' and description 'Check if KiCAD UI is currently running' indicate a status query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_kicad_ui 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 check_kicad_ui, this is the rule to start with:

check_kicad_ui Allowed

check_kicad_ui is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_kicad_ui": {}
  }
}

ALLOW ONLY 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 check_kicad_ui call is checked against it from then on.

FAQ

Questions about check_kicad_ui

What does the check_kicad_ui tool do? +

Check if KiCAD UI is currently running. It is categorised as a Read tool in the KiCAD-MCP-Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_kicad_ui? +

Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for check_kicad_ui: 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 check_kicad_ui? +

check_kicad_ui is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_kicad_ui? +

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

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

check_kicad_ui 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 231 KiCAD-MCP-Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →