edi_validate
Runs the structural checks a trading partner runs before rejecting a file: control numbers matching between the ISA/IEA, GS/GE and ST/SE header and trailer pairs, declared counts matching actual counts, and - for an 856 - the HL hierarchy. HL faults are the usual cause of ASN rejections and charg...
This record as markdown: /tools/com-fluentedi-tools/edi-validate.md
What edi_validate does on Tools
AI agents call edi_validate to retrieve information from Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | string | Yes | Raw X12 EDI text. |
require_levels | array | — | HL level codes that must be present in an 856, e.g. ["S","O","P","I"] for a pack-level ASN. |
Parameters from the server's own tool schema.
Why edi_validate is rated Low
Even though edi_validate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs edi_validate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For edi_validate, this is the rule to start with:
edi_validate 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 Tools, apply this rule, and every edi_validate call is checked against it from then on.
Questions about edi_validate
Runs the structural checks a trading partner runs before rejecting a file: control numbers matching between the ISA/IEA, GS/GE and ST/SE header and trailer pairs, declared counts matching actual counts, and - for an 856 - the HL hierarchy. HL faults are the usual cause of ASN rejections and chargebacks: a parent ID naming no existing node, a duplicate HL01, an unknown level code, a missing carton level. Every finding names the segment and states what the value should have been. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
edi_validate accepts 2 parameters: input, require_levels. Required: input. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for edi_validate: 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 Tools. Nothing to install.
edi_validate 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 edi_validate 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 edi_validate. 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.
edi_validate is provided by the Tools MCP server (https://fluentedi.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tools, and thousands of servers like it.
This server
Across the catalogue