Low Risk

check_kicad_ui

Check if KiCAD UI is currently running

How to control check_kicad_ui ↓

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 — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why check_kicad_ui needs a policy

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.

Documented attack patterns abuse exactly the kind of access check_kicad_ui gives an agent:

How to control check_kicad_ui

PolicyLayer is an MCP gateway — it sits between your AI agents and KiCAD-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_kicad_ui:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_kicad_ui": {}
  }
}

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

  1. Create a free account and register KiCAD-MCP-Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every KiCAD-MCP-Server tool call.

Start from KiCAD-MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

157 KiCAD-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.