check_placement

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

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

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/altium-mcp-suite/check-placement.md

WHAT IT DOES

What check_placement does on Altium-MCP-Suite

AI agents call check_placement to retrieve information from Altium-MCP-Suite without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_placement is rated Low

In the context of Altium (PCB design software), 'check_placement' most likely validates or queries the placement state of components on a PCB. This is a read operation with no side effects. However, confidence is lowered to 0.7 because the description is empty, leaving some ambiguity about whether it could perform validation that blocks workflows or reports errors.

From the tool's definition Tool name 'check_placement' with empty description suggests a query or inspection function. Sibling tools on this server include read-only operations like 'get_all_component_property_names', 'get_all_designators', 'get_all_nets', and…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_placement Allowed

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

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

FAQ

Questions about check_placement

What does the check_placement tool do? +

check_placement is a read tool on the Altium-MCP-Suite MCP server. It is categorised as a Read tool in the Altium-MCP-Suite MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_placement? +

Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for check_placement: 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 check_placement? +

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

Can I rate-limit check_placement? +

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

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

check_placement 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

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