This record as markdown: /tools/eda-agent/app-get-report.md
What app_get_report does on Eda Agent
AI agents call app_get_report 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 app_get_report is rated Low
The 'get_' prefix indicates data retrieval. Although the description is empty, reducing confidence slightly, the tool appears designed to fetch or generate reports from Altium Designer's state without modifying design data. No evidence of side effects, code execution, or destructive operations. Classified as Read with low severity due to the limited blast radius of retrieving design reports.
From the tool's definition Tool name 'app_get_report' follows a retrieval pattern (get_*) consistent with read-only operations. No description provided, but naming convention and context within a design automation suite suggests report generation/retrieval.
Attacks that exploit this kind of access
The rule that runs app_get_report 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 app_get_report, this is the rule to start with:
app_get_report 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 app_get_report call is checked against it from then on.
Questions about app_get_report
app_get_report 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 app_get_report: 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.
app_get_report 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 app_get_report 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 app_get_report. 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.
app_get_report 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