This record as markdown: /tools/eda-agent/obj-copy.md
What obj_copy does on Eda Agent
AI agents use obj_copy 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_copy is rated Medium
'obj_copy' most likely creates duplicates of design objects (schematic components, PCB elements, library items, etc.), which is a write operation—it modifies project state reversibly. Without a description, confidence is moderate (0.75). The severity is medium because misuse by an AI agent could clutter designs or create unwanted duplicates, but the action is undoable via undo or deletion.
From the tool's definition Tool name 'obj_copy' suggests it creates or modifies data by copying design objects within Altium Designer.
Attacks that exploit this kind of access
The rule that runs obj_copy 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_copy, this is the rule to start with:
obj_copy 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_copy call is checked against it from then on.
Questions about obj_copy
obj_copy 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_copy: 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_copy 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_copy 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_copy. 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_copy 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