strings_export_repo_sync · Phrase MCP: Risk & Policy

WHAT IT DOES

What strings_export_repo_sync does on Phrase

AI agents use strings_export_repo_sync 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.

WHY IT NEEDS A POLICY

Why strings_export_repo_sync needs a policy

While export operations might seem read-like, this tool explicitly syncs/writes translations to a repository provider, which constitutes data modification. The async nature and multi-step process increase the blast radius if misused by an agent (e.g., overwriting translations in the wrong repository). However, it's not Destructive because the operation is reversible—translations can be re-synced or reverted.

From the tool's definition Tool performs 'Export translations from Phrase Strings to a repository provider' which involves writing/syncing data to an external repository.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

strings_export_repo_sync Rate-limited

strings_export_repo_sync 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": {
    "strings_export_repo_sync": {
      "limits": [
        {
          "counter": "strings_export_repo_sync_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 Phrase, so you can run agents against it safely.

FAQ

Questions about strings_export_repo_sync

What does the strings_export_repo_sync tool do? +

Export translations from Phrase Strings to a repository provider according to the .phrase.yml file. Export is asynchronous and may take several seconds. 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.

How do I enforce a policy on strings_export_repo_sync? +

Register the Phrase MCP server in PolicyLayer and add a rule for strings_export_repo_sync: 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.

What risk level is strings_export_repo_sync? +

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

Can I rate-limit strings_export_repo_sync? +

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

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

strings_export_repo_sync 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.