proj_get_differences
A read tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/proj-get-differences.md
What proj_get_differences does on Eda Agent
AI agents call proj_get_differences 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.
Why proj_get_differences is rated Low
This tool appears to retrieve or compute differences between project versions or states, which is consistent with Read category operations (search, list, get, fetch). While the empty description reduces confidence slightly, the naming convention 'get_' combined with the context of an Altium Designer automation server suggests it performs a comparison query rather than executing commands, modifying data, or causing…
From the tool's definition Tool name 'proj_get_differences' indicates a query or retrieval operation that compares project states. The 'get_' prefix strongly suggests data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs proj_get_differences 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_differences, this is the rule to start with:
proj_get_differences is read-only, so it stays allowed. 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_get_differences call is checked against it from then on.
Questions about proj_get_differences
proj_get_differences is a read tool on the Eda Agent MCP server. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.
Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_get_differences: 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_get_differences is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the proj_get_differences 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_get_differences. 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_get_differences 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