obj_deselect_all
Clear all object selection on the active document.
This record as markdown: /tools/eda-agent/obj-deselect-all.md
What obj_deselect_all does on Eda Agent
AI agents use obj_deselect_all to create or update resources in Eda Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eda Agent environment.
Why obj_deselect_all is rated Medium
Deselecting objects modifies the UI/selection state of the active document. It is reversible (objects can be re-selected) and has no destructive or data-loss implications. It counts as a Write since it changes document state, but severity is low as no persistent data is permanently altered.
From the tool's definition Clear all object selection on the active document
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs obj_deselect_all 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_deselect_all, this is the rule to start with:
obj_deselect_all stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_deselect_all call is checked against it from then on.
Questions about obj_deselect_all
Clear all object selection on the active document. It is categorised as a Write tool in the Eda Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eda Agent MCP server in PolicyLayer and add a rule for obj_deselect_all: 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_deselect_all is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the obj_deselect_all 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_deselect_all. 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_deselect_all 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