proj_get_parameters

Get all parameters defined at the project level.

SERVEREda Agent SOURCEsalitronic/eda-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/proj-get-parameters.md

WHAT IT DOES

What proj_get_parameters does on Eda Agent

AI agents call proj_get_parameters to retrieve information from Eda Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why proj_get_parameters is rated Low

This tool queries and returns parameter metadata from an Altium Designer project. It is a read-only retrieval operation with no side effects. The blast radius of misuse is minimal: an attacker gains visibility into project parameters but cannot modify designs, execute code, delete data, or commit financial transactions. It belongs in the Read category with low severity.

From the tool's definition 'Get all parameters defined at the project level' — retrieves project-level configuration data with no modification, deletion, or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

proj_get_parameters Allowed

proj_get_parameters is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proj_get_parameters": {}
  }
}

ALLOW ONLY 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_get_parameters call is checked against it from then on.

FAQ

Questions about proj_get_parameters

What does the proj_get_parameters tool do? +

Get all parameters defined at the project level. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on proj_get_parameters? +

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

What risk level is proj_get_parameters? +

proj_get_parameters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit proj_get_parameters? +

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

How do I block proj_get_parameters completely? +

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

What MCP server provides proj_get_parameters? +

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

KEEP EXPLORING

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

This server

All 345 Eda Agent tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →