edi.edifact-generate · MCP: Risk & Policy

WHAT IT DOES

What edi.edifact-generate does on Mcp

AI agents use edi.edifact-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.edifact-generate needs a policy

This tool creates outbound EDI documents (EDIFACT) which are standardized electronic business documents used internationally for procurement, invoicing, shipping, and customs declarations. While not irreversible (hence not Destructive), generating and sending EDI documents commits trading partners to formal business transactions and obligations. The POST operation indicates transmission of created documents.

From the tool's definition Tool description explicitly states 'Generate an outbound UN/EDIFACT document' and is marked 'POST type', indicating it creates and sends structured business documents that represent electronic data interchange commitments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

edi.edifact-generate Rate-limited

edi.edifact-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.edifact-generate": {
      "limits": [
        {
          "counter": "edi.edifact-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.edifact-generate

What does the edi.edifact-generate tool do? +

Generate an outbound UN/EDIFACT document from JSON (international counterpart to edi.generate/X12). POST type (. 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.edifact-generate? +

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

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

Can I rate-limit edi.edifact-generate? +

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

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

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