AI agents invoke strings_start_job 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 asynchronous operation (starting a job) in an external system (Phrase Strings localization platform). The effects are not immediately reversible through this single call and depend on the arguments passed. This qualifies as Execute rather than Write because it initiates a background process/workflow rather than directly creating a simple data record.
From the tool's definition Tool name 'strings_start_job' with description 'Start a draft job in a Phrase Strings project' indicates triggering an external operation (job initiation) whose effects depend on which project and job parameters are provided.
Attacks that exploit this kind of access
Start a draft job in a Phrase Strings project. 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_start_job: 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_start_job 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_start_job 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_start_job. 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_start_job 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 →