sch_get_directives
A read tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/sch-get-directives.md
What sch_get_directives does on Eda Agent
AI agents call sch_get_directives 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 sch_get_directives is rated Low
The 'get_' prefix universally indicates read operations that query or retrieve state without side effects. In a schematic design context, 'directives' are likely design rules, annotations, or metadata that would be retrieved for inspection or review purposes, consistent with the server's stated 'design review' and 'audits' capabilities. No mutation, execution, or destructive potential is evident from the name alone.
From the tool's definition Tool name 'sch_get_directives' uses the 'get_' verb pattern, indicating retrieval of schematic directives with no modification capability. The server context shows this is part of Altium Designer automation (a PCB/schematic design tool).
Attacks that exploit this kind of access
The rule that runs sch_get_directives 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 sch_get_directives, this is the rule to start with:
sch_get_directives 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 sch_get_directives call is checked against it from then on.
Questions about sch_get_directives
sch_get_directives 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 sch_get_directives: 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.
sch_get_directives 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 sch_get_directives 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 sch_get_directives. 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.
sch_get_directives 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