proj_export_step

A write tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/proj-export-step.md

WHAT IT DOES

What proj_export_step does on Eda Agent

AI agents use proj_export_step 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.

RISK

Why proj_export_step is rated Medium

Export tools are Write-category because they generate new data (STEP files in this case, a standard 3D CAD format) as artifacts. The severity is medium because exporting design data could expose proprietary designs or intellectual property if misused by an agent, but the operation itself is reversible and non-destructive to the source project.

From the tool's definition Tool name 'proj_export_step' indicates export functionality, which produces new output files or data artifacts from a project. The prefix 'proj_' confirms it operates on project state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proj_export_step 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_export_step, this is the rule to start with:

proj_export_step Rate-limited

proj_export_step 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proj_export_step": {
      "limits": [
        {
          "counter": "proj_export_step_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every proj_export_step call is checked against it from then on.

FAQ

Questions about proj_export_step

What does the proj_export_step tool do? +

proj_export_step 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.

How do I enforce a policy on proj_export_step? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_export_step: 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.

What risk level is proj_export_step? +

proj_export_step is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit proj_export_step? +

Yes. Add a rate_limit block to the proj_export_step 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.

How do I block proj_export_step completely? +

Set action: deny in the PolicyLayer policy for proj_export_step. 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.

What MCP server provides proj_export_step? +

proj_export_step 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.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 345 Eda Agent tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →