obj_switch_view
Toggle between 2D and 3D view for PCB documents.
This record as markdown: /tools/eda-agent/obj-switch-view.md
What obj_switch_view does on Eda Agent
AI agents invoke obj_switch_view 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_switch_view is rated High
This tool triggers a view change operation in the Altium Designer application — an external operation that changes the rendering/display state of the PCB document. It doesn't simply read data, nor does it create/modify design data or destroy anything. It executes a UI/view state change in the application, which fits the Execute category.
From the tool's definition Toggle between 2D and 3D view for PCB documents
Attacks that exploit this kind of access
The rule that runs obj_switch_view 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_switch_view, this is the rule to start with:
obj_switch_view 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_switch_view call is checked against it from then on.
Questions about obj_switch_view
Toggle between 2D and 3D view for PCB documents. 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_switch_view: 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_switch_view 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_switch_view 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_switch_view. 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_switch_view 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