proj_lock_designator
A write tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/proj-lock-designator.md
What proj_lock_designator does on Eda Agent
AI agents use proj_lock_designator 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 proj_lock_designator is rated Medium
The tool name indicates a state modification (locking) of designators (component identifiers) in a project context. This is a reversible Write operation—designators can be unlocked later. While the empty description limits certainty, the naming convention and server context (persistent DelphiScript bridge for design automation) suggest it modifies project data rather than executing arbitrary code or deleting data.
From the tool's definition Tool name 'proj_lock_designator' suggests modifying designator lock state in Altium Designer projects. Given the server's scope (290+ design automation tools), this likely creates or modifies designator locking metadata reversibly.
Attacks that exploit this kind of access
The rule that runs proj_lock_designator 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 proj_lock_designator, this is the rule to start with:
proj_lock_designator 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 proj_lock_designator call is checked against it from then on.
Questions about proj_lock_designator
proj_lock_designator 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 proj_lock_designator: 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.
proj_lock_designator 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 proj_lock_designator 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 proj_lock_designator. 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.
proj_lock_designator 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