export_xliff_file · Xliff Processor MCP: Risk & Policy

WHAT IT DOES

What export_xliff_file does on Xliff Processor

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

WHY IT NEEDS A POLICY

Why export_xliff_file needs a policy

Export operations typically create or write output files, which is reversible (files can be deleted or overwritten). The tool likely serializes processed XLIFF data to a file. Without explicit deletion/overwrite semantics in the description, this is Write rather than Destructive.

From the tool's definition Tool name 'export_xliff_file' indicates file export/output operation. Server context shows XLIFF processing for 'manipulation of translation units in localization workflows.' Empty description limits certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_xliff_file Rate-limited

export_xliff_file 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": {
    "export_xliff_file": {
      "limits": [
        {
          "counter": "export_xliff_file_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 Xliff Processor, so you can run agents against it safely.

FAQ

Questions about export_xliff_file

What does the export_xliff_file tool do? +

export_xliff_file. It is categorised as a Write tool in the Xliff Processor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_xliff_file? +

Register the Xliff Processor MCP server in PolicyLayer and add a rule for export_xliff_file: 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 Xliff Processor. Nothing to install.

What risk level is export_xliff_file? +

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

Can I rate-limit export_xliff_file? +

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

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

export_xliff_file is provided by the Xliff Processor MCP server (langlink-localization/xliff-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.