sch_place_no_erc

A write tool on the Altium-MCP-Suite MCP server.

SERVERAltium-MCP-Suite SOURCEM-R-Abedini/Altium-MCP-Suite

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/altium-mcp-suite/sch-place-no-erc.md

WHAT IT DOES

What sch_place_no_erc does on Altium-MCP-Suite

AI agents use sch_place_no_erc to create or update resources in Altium-MCP-Suite, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Altium-MCP-Suite environment.

RISK

Why sch_place_no_erc is rated Medium

The name suggests placing (creating) a No-ERC (No Electrical Rules Check) directive marker in a schematic. This is a reversible write/modification to the schematic design. Description is empty, which lowers confidence. Based on naming convention with sibling tools and Altium Designer context, this likely places a suppression marker on a schematic net or pin.

From the tool's definition Tool name 'sch_place_no_erc' suggests placing a No-ERC marker on a schematic, which is a write operation that modifies schematic data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sch_place_no_erc safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Altium-MCP-Suite, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sch_place_no_erc, this is the rule to start with:

sch_place_no_erc Rate-limited

sch_place_no_erc stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sch_place_no_erc": {
      "limits": [
        {
          "counter": "sch_place_no_erc_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Altium-MCP-Suite, apply this rule, and every sch_place_no_erc call is checked against it from then on.

FAQ

Questions about sch_place_no_erc

What does the sch_place_no_erc tool do? +

sch_place_no_erc is a write tool on the Altium-MCP-Suite MCP server. It is categorised as a Write tool in the Altium-MCP-Suite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sch_place_no_erc? +

Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for sch_place_no_erc: 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 Altium-MCP-Suite. Nothing to install.

What risk level is sch_place_no_erc? +

sch_place_no_erc is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sch_place_no_erc? +

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

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

sch_place_no_erc is provided by the Altium-MCP-Suite MCP server (M-R-Abedini/Altium-MCP-Suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Altium-MCP-Suite, and thousands of servers like it.

This server

All 817 Altium-MCP-Suite tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →