design_generate_bom
A write tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/design-generate-bom.md
What design_generate_bom does on Eda Agent
AI agents use design_generate_bom 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 design_generate_bom is rated Medium
BOM generation is a write operation—it produces new data artifacts (the BOM document/file) that are reversible (can be regenerated or deleted). However, the empty description introduces uncertainty about exact behavior: it could be read-only (merely extracting existing BOM data) or write-focused (materializing a new BOM export).
From the tool's definition Tool name 'design_generate_bom' indicates generation of a Bill of Materials artifact, which is a derived data product.
Attacks that exploit this kind of access
The rule that runs design_generate_bom 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 design_generate_bom, this is the rule to start with:
design_generate_bom 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 design_generate_bom call is checked against it from then on.
Questions about design_generate_bom
design_generate_bom 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 design_generate_bom: 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.
design_generate_bom 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 design_generate_bom 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 design_generate_bom. 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.
design_generate_bom 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