proj_sync_pcb

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-sync-pcb.md

WHAT IT DOES

What proj_sync_pcb does on Eda Agent

AI agents use proj_sync_pcb 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_sync_pcb is rated Medium

The tool is classified as Write rather than Execute because 'sync' implies reversible data modification (updating PCB project state) rather than arbitrary code execution. However, severity is elevated to 'high' because PCB synchronization in an industrial design tool could corrupt design integrity if misapplied, and the empty description prevents confirmation that the operation is fully reversible.

From the tool's definition Tool name 'proj_sync_pcb' indicates synchronization of PCB project state. The description is empty, but the context of 290+ tools for 'schematic, PCB, library & project automation' over a persistent DelphiScript bridge suggests this tool modifies design data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

proj_sync_pcb Rate-limited

proj_sync_pcb 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_sync_pcb": {
      "limits": [
        {
          "counter": "proj_sync_pcb_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_sync_pcb call is checked against it from then on.

FAQ

Questions about proj_sync_pcb

What does the proj_sync_pcb tool do? +

proj_sync_pcb 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_sync_pcb? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_sync_pcb: 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_sync_pcb? +

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

Can I rate-limit proj_sync_pcb? +

Yes. Add a rate_limit block to the proj_sync_pcb 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_sync_pcb completely? +

Set action: deny in the PolicyLayer policy for proj_sync_pcb. 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_sync_pcb? +

proj_sync_pcb 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 →