replace_xliff_targets
AI agents use replace_xliff_targets 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.
The tool modifies existing translation target content within XLIFF files, which is a reversible write operation. While the description is empty, the name unambiguously indicates data mutation rather than deletion or execution of arbitrary code.
From the tool's definition Tool name 'replace_xliff_targets' indicates modification of XLIFF translation target content. XLIFF files contain translation units with source and target segments; 'replace' clearly indicates overwriting/updating target translations.
Attacks that exploit this kind of access
replace_xliff_targets. 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.
Register the Xliff Processor MCP server in PolicyLayer and add a rule for replace_xliff_targets: 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.
replace_xliff_targets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the replace_xliff_targets 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 replace_xliff_targets. 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.
replace_xliff_targets 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.
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 →