lib_set_current_component
A write tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/lib-set-current-component.md
What lib_set_current_component does on Eda Agent
AI agents use lib_set_current_component to create or update resources in Eda Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eda Agent environment.
Why lib_set_current_component is rated Medium
The tool performs a write operation by changing which component is selected/active in the library context. While reversible (can be set to a different component), it modifies application state.
From the tool's definition Tool name is 'lib_set_current_component' which indicates modification of library state by setting the current component.
Attacks that exploit this kind of access
The rule that runs lib_set_current_component 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_set_current_component, this is the rule to start with:
lib_set_current_component stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_set_current_component call is checked against it from then on.
Questions about lib_set_current_component
lib_set_current_component is a write tool on the Eda Agent MCP server. It is categorised as a Write tool in the Eda Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eda Agent MCP server in PolicyLayer and add a rule for lib_set_current_component: 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_set_current_component is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lib_set_current_component 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_set_current_component. 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_set_current_component 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