edi.generate · MCP: Risk & Policy

WHAT IT DOES

What edi.generate does on Mcp

AI agents use edi.generate to create or update resources in Mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.

WHY IT NEEDS A POLICY

Why edi.generate needs a policy

This tool creates EDI documents (Purchase Orders or Invoices) from structured data. It's a document generation/creation action — reversible in the sense that the document is returned as output rather than automatically transmitted. However, the server description notes 'pay-per-call tools settled in USDC,' which means each call has a financial cost.

From the tool's definition Generate an outbound ANSI X12 EDI document from JSON... Returns the full X12 interchange in meta.edi

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

edi.generate Rate-limited

edi.generate 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edi.generate": {
      "limits": [
        {
          "counter": "edi.generate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp, so you can run agents against it safely.

FAQ

Questions about edi.generate

What does the edi.generate tool do? +

Generate an outbound ANSI X12 EDI document from JSON. POST type (850 = Purchase Order, 810 = Invoice) + senderId, receiverId, documentNumber (PO#/invoice#), optional date, parties (N1 role+name), items (quantity, uom, price, productId); for 810 optionally poNumber + total. Returns the full X12 interchange in meta.edi (correct ISA/GS/ST…SE/GE/IEA envelope). Deterministic — the outbound complement to edi.parse + edi.ack. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on edi.generate? +

Register the MCP server in PolicyLayer and add a rule for edi.generate: 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.

What risk level is edi.generate? +

edi.generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit edi.generate? +

Yes. Add a rate_limit block to the edi.generate 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.

How do I block edi.generate completely? +

Set action: deny in the PolicyLayer policy for edi.generate. 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.

What MCP server provides edi.generate? +

edi.generate 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.