obj_batch_create
A write tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/obj-batch-create.md
What obj_batch_create does on Eda Agent
AI agents use obj_batch_create 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 obj_batch_create is rated Medium
The tool name strongly suggests batch object creation within Altium Designer's design context (schematics, PCB, libraries, projects). This is a Write operation—it creates or modifies design artifacts reversibly. Severity is medium because batch creation in a design tool could affect multiple design elements, but changes are typically reversible via undo.
From the tool's definition Tool name 'obj_batch_create' indicates creation of multiple objects. The 'batch_create' pattern commonly creates or adds multiple items. Context: Altium Designer automation server with 290+ tools for schematic, PCB, and library design.
Attacks that exploit this kind of access
The rule that runs obj_batch_create 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 obj_batch_create, this is the rule to start with:
obj_batch_create 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 obj_batch_create call is checked against it from then on.
Questions about obj_batch_create
obj_batch_create 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 obj_batch_create: 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.
obj_batch_create 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 obj_batch_create 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 obj_batch_create. 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.
obj_batch_create 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