proj_import_document
A write tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/proj-import-document.md
What proj_import_document does on Eda Agent
AI agents use proj_import_document 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_import_document is rated Medium
The tool appears to import and add a document to a project, which modifies project state reversibly. Without an explicit description, confidence is moderate. This is categorized as Write rather than Execute because import typically means loading/registering existing data into a project structure rather than executing arbitrary commands.
From the tool's definition Tool name 'proj_import_document' indicates creation/addition of a document to a project; this is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs proj_import_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_import_document, this is the rule to start with:
proj_import_document 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_import_document call is checked against it from then on.
Questions about proj_import_document
proj_import_document 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_import_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_import_document 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_import_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_import_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_import_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.
This server
Across the catalogue