audit_find_pads_near_board_edge
A read tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/audit-find-pads-near-board-edge.md
What audit_find_pads_near_board_edge does on Eda Agent
AI agents call audit_find_pads_near_board_edge 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 audit_find_pads_near_board_edge is rated Low
Despite the empty description lowering confidence slightly, the naming convention strongly indicates this is a read-only audit operation that detects a design condition without modifying, executing, or deleting anything. It retrieves information about pad placement relative to board geometry, which is a classic Read category function. No side effects are expected from running this query.
From the tool's definition Tool name 'audit_find_pads_near_board_edge' indicates a passive inspection/audit function that searches for and reports pads positioned near board edges. The 'audit_' prefix suggests read-only analysis.
Attacks that exploit this kind of access
The rule that runs audit_find_pads_near_board_edge 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 audit_find_pads_near_board_edge, this is the rule to start with:
audit_find_pads_near_board_edge 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 audit_find_pads_near_board_edge call is checked against it from then on.
Questions about audit_find_pads_near_board_edge
audit_find_pads_near_board_edge 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 audit_find_pads_near_board_edge: 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.
audit_find_pads_near_board_edge 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 audit_find_pads_near_board_edge 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 audit_find_pads_near_board_edge. 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.
audit_find_pads_near_board_edge 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