proj_push_parameters
A write tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/proj-push-parameters.md
What proj_push_parameters does on Eda Agent
AI agents use proj_push_parameters 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_push_parameters is rated Medium
This tool operates on persistent design project state within Altium Designer. While the description is empty (lowering confidence slightly), the name and server context indicate it modifies project parameters reversibly. This is a Write operation rather than Execute because it appears to set configuration values rather than execute arbitrary commands.
From the tool's definition Tool name 'proj_push_parameters' indicates modification of project parameters. The verb 'push' combined with 'parameters' in the context of Altium Designer (a PCB/schematic design tool) suggests writing or updating configuration settings that control design…
Attacks that exploit this kind of access
The rule that runs proj_push_parameters 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_push_parameters, this is the rule to start with:
proj_push_parameters 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_push_parameters call is checked against it from then on.
Questions about proj_push_parameters
proj_push_parameters 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_push_parameters: 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_push_parameters 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_push_parameters 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_push_parameters. 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_push_parameters 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