sch_generate_toc
A write tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/sch-generate-toc.md
What sch_generate_toc does on Eda Agent
AI agents use sch_generate_toc 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_generate_toc is rated Medium
The tool appears to create or modify schematic documentation by generating a table of contents. This is a Write operation—it produces new data (the TOC) that modifies the schematic's documentation structure, though reversibly. Severity is medium because misuse could corrupt or pollute schematic metadata, but the impact is scoped to documentation rather than core design logic.
From the tool's definition Tool name 'sch_generate_toc' suggests generation of table-of-contents for schematic documents. The 'generate' verb and suffix '_toc' indicate creation of a new artifact or document structure modification. Empty description reduces specificity.
Attacks that exploit this kind of access
The rule that runs sch_generate_toc 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_generate_toc, this is the rule to start with:
sch_generate_toc 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_generate_toc call is checked against it from then on.
Questions about sch_generate_toc
sch_generate_toc 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_generate_toc: 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_generate_toc 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_generate_toc 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_generate_toc. 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_generate_toc 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