This record as markdown: /tools/eda-agent/sch-place-note.md
What sch_place_note does on Eda Agent
AI agents use sch_place_note 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 sch_place_note is rated Medium
The tool name suggests creation/insertion of a note object in a schematic, which modifies the design document reversibly (notes can be edited or deleted). This is a Write operation rather than Read (it changes state), Execute (no arbitrary code execution), or Destructive (reversible).
From the tool's definition Tool name 'sch_place_note' indicates placement of a note within a schematic, which creates or adds an annotation artifact to the design document. No description provided, limiting certainty.
Attacks that exploit this kind of access
The rule that runs sch_place_note 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_place_note, this is the rule to start with:
sch_place_note 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 sch_place_note call is checked against it from then on.
Questions about sch_place_note
sch_place_note is a write tool on the Eda Agent MCP server. 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 sch_place_note: 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_place_note 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 sch_place_note 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_place_note. 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_place_note 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