audit_find_bad_connections
A read tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/audit-find-bad-connections.md
What audit_find_bad_connections does on Eda Agent
AI agents call audit_find_bad_connections 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_bad_connections is rated Low
Despite empty description, the name strongly suggests this is a diagnostic/inspection tool that identifies connectivity issues in designs without modifying state. Audit operations are typically read-only. No side effects implied. Confidence reduced from high due to missing description, but naming pattern is clear.
From the tool's definition Tool name 'audit_find_bad_connections' indicates querying/inspection; 'audit' prefix suggests read-only review operation within Altium Designer schematics or PCB connectivity analysis.
Attacks that exploit this kind of access
The rule that runs audit_find_bad_connections 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_bad_connections, this is the rule to start with:
audit_find_bad_connections 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_bad_connections call is checked against it from then on.
Questions about audit_find_bad_connections
audit_find_bad_connections 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_bad_connections: 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_bad_connections 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_bad_connections 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_bad_connections. 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_bad_connections 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