Import terms into a Phrase TMS translation memory. Provide either file_path (host filesystem path, for local MCP server use) or file_content + file_name (base64-encoded file bytes, for Claude Desktop uploaded files). (POST /api2/v1/transMemories/{tmUid}/import)
AI agents use tms_import_trans_memory to create or update resources in Phrase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Phrase environment.
This tool creates or modifies data in the translation memory by importing terms, which is a reversible operation (imported terms can be edited or removed). It does not delete data irreversibly (Destructive), execute arbitrary code (Execute), or move money (Financial). The 'import' action adds or updates translation memory content, fitting the Write category.
From the tool's definition Tool description states "Import terms into a Phrase TMS translation memory"; the API endpoint is POST /api2/v1/transMemories/{tmUid}/import, which creates/adds new data to a translation memory resource.
Attacks that exploit this kind of access
Import terms into a Phrase TMS translation memory. Provide either file_path (host filesystem path, for local MCP server use) or file_content + file_name (base64-encoded file bytes, for Claude Desktop uploaded files). (POST /api2/v1/transMemories/{tmUid}/import). It is categorised as a Write tool in the Phrase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Phrase MCP server in PolicyLayer and add a rule for tms_import_trans_memory: 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 Phrase. Nothing to install.
tms_import_trans_memory 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 tms_import_trans_memory 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 tms_import_trans_memory. 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.
tms_import_trans_memory is provided by the Phrase MCP server (phrase-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 →