get_drc_history_tool

THE RISK

Low Risk

Why get_drc_history_tool needs a policy

This tool retrieves Design Rule Check history from a KiCad project, which is a read-only query operation. It fetches existing data (DRC history entries) without creating, modifying, or deleting any project data. The blast radius of misuse is minimal—an attacker could only view design check records they already have file access to.

From the tool's definition Tool description states 'Get the DRC check history' and 'Returns: Dictionary with DRC history entries'. The verb 'get' and return of historical data indicates retrieval without modification. No side effects are described.

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

POLICY

How to control get_drc_history_tool

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

policy.json

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

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

Create a free account and register KiCad MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More KiCad MCP Server tools

Execute run_drc_check Run a Design Rule Check on a KiCad PCB file. Args: project_pa Execute generate_pcb_thumbnail Generate a thumbnail image of a KiCad PCB layout using kicad-cli. Args: Execute generate_project_thumbnail Generate a thumbnail of a KiCad project's PCB layout (Alias for generate_pcb_thumbnail). Execute open_project Open a KiCad project in KiCad. Write export_bom_csv Export a Bill of Materials for a KiCad project. This tool attempts to gen Read analyze_bom Analyze a KiCad project's Bill of Materials. This tool will look for BOM Read analyze_project_circuit_patterns Identify circuit patterns in a KiCad project's schematic. Args: Read analyze_schematic_connections Analyze connections in a KiCad schematic. This tool provides detailed ana

All 16 KiCad MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_drc_history_tool

What does the get_drc_history_tool tool do? +

Get the DRC check history for a KiCad project. Args: project_path: Path to the KiCad project file (.kicad_pro) Returns: Dictionary with DRC history entries. 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_drc_history_tool? +

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

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

Can I rate-limit get_drc_history_tool? +

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

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

get_drc_history_tool is provided by the KiCad MCP Server MCP server (lamaalrajih/kicad-mcp). 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.

CHECK YOUR STACK →