Parse a raw UN/EDIFACT document (the B2B EDI standard used across Europe, Asia, logistics and customs — international counterpart to ANSI X12) into clean structured JSON. POST edi with the raw interchange text. Reads the optional UNA service-string advice to auto-detect delimiters (or applies UN ...
AI agents call edi.edifact to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's sole purpose is parsing and reading EDI interchange data into JSON format. It performs data extraction and transformation without side effects, reversibility concerns, code execution, data deletion, or financial movement. This is a pure Read operation with minimal risk even if misused—an AI could incorrectly parse a document but cannot alter the source or cause cascading damage.
From the tool's definition Parse a raw UN/EDIFACT document...into clean structured JSON. Reads the optional UNA service-string advice...returns the interchange envelope...every segment named.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Parse a raw UN/EDIFACT document (the B2B EDI standard used across Europe, Asia, logistics and customs — international counterpart to ANSI X12) into clean structured JSON. POST edi with the raw interchange text. Reads the optional UNA service-string advice to auto-detect delimiters (or applies UN defaults); handles release-character escaping; returns the interchange envelope (UNB: sender/recipient with qualifiers, date/time, control reference, test indicator) and each message with its type decoded (ORDERS PO, INVOIC invoice, DESADV ASN, ORDRSP PO response, CONTRL ack), every segment named (BGM, DTM, NAD, LIN, QTY, MOA…), and a semantic summary (order/invoice numbers, dates, parties with role decoded, line items, totals). Deterministic, no external calls. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for edi.edifact: 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 Mcp. Nothing to install.
edi.edifact 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.edifact 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.edifact. 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.edifact is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →