Low Risk

get_net_at_point

Returns the net name at a given (x, y) coordinate in a schematic, or null if no net label

How to control get_net_at_point ↓

What get_net_at_point does on KiCAD-MCP-Server

AI agents call get_net_at_point 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 get_net_at_point needs a policy

This tool queries and retrieves data (a net name) from a given coordinate in a schematic. It has no side effects, does not create, modify, delete, or execute any operations. It is a pure read operation consistent with the 'Read' category definition.

From the tool's definition Tool name 'get_net_at_point' and description 'Returns the net name at a given (x, y) coordinate in a schematic, or null if no net label' indicate a read-only query operation that retrieves information without modifying state.

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

How to control get_net_at_point

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 get_net_at_point:

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

get_net_at_point 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 get_net_at_point

What does the get_net_at_point tool do? +

Returns the net name at a given (x, y) coordinate in a schematic, or null if no net label. 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 get_net_at_point? +

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

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

Can I rate-limit get_net_at_point? +

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

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

get_net_at_point 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.