AI agents invoke strings_activate_repo_sync to trigger actions in Phrase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an operational state change that enables automated external operations (imports triggered by repository pushes, import/export of translations). It activates a system integration that causes ongoing side effects depending on repository activity, making it an Execute-category action. Misuse could cause unintended mass import/export of translation data across systems.
From the tool's definition Activate a deactivated Repo Sync. Active syncs can be used to import and export translations, and imports are automatically triggered by pushes to the repository if configured.
Attacks that exploit this kind of access
Activate a deactivated Repo Sync. Active syncs can be used to import and export translations, and imports are automatically triggered by pushes to the repository if configured. It is categorised as a Execute tool in the Phrase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Phrase MCP server in PolicyLayer and add a rule for strings_activate_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.
strings_activate_repo_sync is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the strings_activate_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.
Set action: deny in the PolicyLayer policy for strings_activate_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.
strings_activate_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.
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 →