This record as markdown: /tools/eda-agent/obj-modify.md
What obj_modify does on Eda Agent
AI agents use obj_modify 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_modify is rated Medium
The tool name strongly suggests reversible modification of design data. Without a detailed description, confidence is moderate but not low, given the clear naming convention and context of a persistent DelphiScript bridge for Altium automation.
From the tool's definition Tool name 'obj_modify' indicates modification of objects. No description provided, but in context of Altium Designer automation with 290+ tools for 'design review, audits, SVG render, connectivity-driven auto-placement, panelization', obj_modify almost…
Attacks that exploit this kind of access
The rule that runs obj_modify 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_modify, this is the rule to start with:
obj_modify 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_modify call is checked against it from then on.
Questions about obj_modify
obj_modify 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_modify: 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_modify 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_modify 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_modify. 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_modify 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