This record as markdown: /tools/eda-agent/obj-query.md
What obj_query does on Eda Agent
AI agents call obj_query 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 obj_query is rated Low
The 'query' nomenclature strongly suggests read-only data retrieval. However, the empty description reduces confidence. Given the context of an Altium design automation server with 290+ tools spanning schematic, PCB, and library operations, a query function most likely retrieves design object properties or metadata. No evidence suggests side effects, data modification, or execution of external commands.
From the tool's definition Tool name 'obj_query' indicates a query operation; description is empty, limiting certainty. In the context of Altium Designer automation, 'query' typically retrieves object properties or design data without modification.
Attacks that exploit this kind of access
The rule that runs obj_query 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_query, this is the rule to start with:
obj_query 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 obj_query call is checked against it from then on.
Questions about obj_query
obj_query 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 obj_query: 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_query 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 obj_query 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_query. 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_query 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