lib_get_components
A read tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/lib-get-components.md
What lib_get_components does on Eda Agent
AI agents call lib_get_components 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 lib_get_components is rated Low
The 'get_' prefix and 'components' noun suggest this retrieves component information from a library, a read-only operation with no side effects. The empty description reduces confidence slightly, but the tool name structure and context within an Altium Designer automation suite (alongside similar query tools like app_get_*) point toward data retrieval rather than write, execute, or destructive operations.
From the tool's definition Tool name 'lib_get_components' contains 'get', which indicates data retrieval. Description is empty, limiting evidence, but the naming pattern suggests querying component library data without modification.
Attacks that exploit this kind of access
The rule that runs lib_get_components 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 lib_get_components, this is the rule to start with:
lib_get_components 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 lib_get_components call is checked against it from then on.
Questions about lib_get_components
lib_get_components 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 lib_get_components: 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.
lib_get_components 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 lib_get_components 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 lib_get_components. 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.
lib_get_components 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