pcb_check_placement_collision
A read tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/pcb-check-placement-collision.md
What pcb_check_placement_collision does on Eda Agent
AI agents call pcb_check_placement_collision to retrieve information from Eda Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pcb_check_placement_collision is rated Low
The verb 'check' combined with 'placement collision' strongly implies the tool queries or validates component placement state and reports conflicts, rather than modifying the design. This aligns with Read category behavior (inspect, diagnose, validate).
From the tool's definition Tool name 'pcb_check_placement_collision' uses 'check' verb, which typically indicates inspection/validation without modification. The 'collision' suggests detection of overlapping components—a read-only diagnostic operation.
Attacks that exploit this kind of access
The rule that runs pcb_check_placement_collision safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pcb_check_placement_collision, this is the rule to start with:
pcb_check_placement_collision is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every pcb_check_placement_collision call is checked against it from then on.
Questions about pcb_check_placement_collision
pcb_check_placement_collision is a read tool on the Eda Agent MCP server. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.
Register the Eda Agent MCP server in PolicyLayer and add a rule for pcb_check_placement_collision: 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 Eda Agent. Nothing to install.
pcb_check_placement_collision is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pcb_check_placement_collision 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.
Set action: deny in the PolicyLayer policy for pcb_check_placement_collision. 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.
pcb_check_placement_collision is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Eda Agent, and thousands of servers like it.
This server
Across the catalogue