proj_remove_document
A destructive tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/proj-remove-document.md
What proj_remove_document does on Eda Agent
AI agents call proj_remove_document to permanently remove resources in Eda Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why proj_remove_document is rated Critical
Although the description is empty, the tool name strongly implies permanent deletion or removal of project documents. In the context of an Altium Designer automation server managing schematics and PCBs, removing a document from a project is typically irreversible and could lose design work. This fits the Destructive category (irreversibly deletes or overwrites data).
From the tool's definition Tool name 'proj_remove_document' indicates removal/deletion of a document from a project. The verb 'remove' combined with 'document' suggests an irreversible action that destroys or purges data.
Attacks that exploit this kind of access
The rule that runs proj_remove_document 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_remove_document, this is the rule to start with:
proj_remove_document is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every proj_remove_document call is checked against it from then on.
Questions about proj_remove_document
proj_remove_document is a destructive tool on the Eda Agent MCP server. It is categorised as a Destructive tool in the Eda Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_remove_document: 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_remove_document is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the proj_remove_document 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_remove_document. 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_remove_document 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.
Across the catalogue