obj_refresh_document
Force a redraw/refresh of the current document.
This record as markdown: /tools/eda-agent/obj-refresh-document.md
What obj_refresh_document does on Eda Agent
AI agents invoke obj_refresh_document to trigger actions in Eda Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why obj_refresh_document is rated High
Triggering a redraw/refresh is an active operation that causes the application to re-render the document. It has side effects (UI update, potential recalculation) but does not read, write, or destroy data. It fits Execute as it triggers an external operation in Altium Designer. Severity is low since misuse would merely cause unnecessary refreshes with no data loss.
From the tool's definition Force a redraw/refresh of the current document
Attacks that exploit this kind of access
The rule that runs obj_refresh_document 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 obj_refresh_document, this is the rule to start with:
obj_refresh_document stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 obj_refresh_document call is checked against it from then on.
Questions about obj_refresh_document
Force a redraw/refresh of the current document. It is categorised as a Execute tool in the Eda Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Eda Agent MCP server in PolicyLayer and add a rule for obj_refresh_document: 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.
obj_refresh_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the obj_refresh_document 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 obj_refresh_document. 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.
obj_refresh_document 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.
Across the catalogue