list_floating_labels

Returns all net labels in the schematic that are not connected to any component pin.

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/list-floating-labels.md

WHAT IT DOES

What list_floating_labels does on KiCAD-MCP-Server

AI agents call list_floating_labels 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 list_floating_labels is rated Low

This is a read-only operation that queries and retrieves data about unconnected net labels. It has no side effects, does not modify the schematic, and does not execute any operations. The worst-case misuse would be an agent gathering information about design issues, which poses minimal risk.

From the tool's definition Tool name and description indicate it 'Returns all net labels in the schematic that are not connected to any component pin' — a query operation that retrieves information without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_floating_labels Allowed

list_floating_labels 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": {
    "list_floating_labels": {}
  }
}

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

FAQ

Questions about list_floating_labels

What does the list_floating_labels tool do? +

Returns all net labels in the schematic that are not connected to any component pin. 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 list_floating_labels? +

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

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

Can I rate-limit list_floating_labels? +

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

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

list_floating_labels 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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