process_tmx
AI agents call process_tmx to retrieve information from Xliff Processor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'process_tmx' suggests processing a TMX (Translation Memory eXchange) file. Based on sibling tools (validate_tmx, export_tmx_file, process_xliff), 'process_tmx' likely parses and reads TMX file content similarly to 'process_xliff'. However, 'manipulation' is mentioned in the server description, so there is some chance it modifies data. With an empty description, confidence is low.
From the tool's definition Tool name 'process_tmx' and server description mentions 'parsing, validation, and manipulation of translation units'. Description is empty and uninformative.
Attacks that exploit this kind of access
process_tmx. It is categorised as a Read tool in the Xliff Processor MCP Server, which means it retrieves data without modifying state.
Register the Xliff Processor MCP server in PolicyLayer and add a rule for process_tmx: 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.
process_tmx 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 process_tmx 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 process_tmx. 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.
process_tmx 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.
process_tmx is one line of Xliff Processor's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →