AI agents use bqe_update_ai_check 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 is classified as Write because the tool creates or modifies data reversibly. It performs a PUT request to update an AI Check configuration, replacing name and qualityRequirements. The blast radius is medium because modifying quality evaluation rules could affect localization workflow and QA processes, but changes are reversible and don't delete data or incur financial obligations.
From the tool's definition Updates an existing AI Check in Phrase Quality Evaluator. Tool uses PUT operation which modifies existing data reversibly (name and qualityRequirements fields can be changed again).
Attacks that exploit this kind of access
Update an existing AI Check in Phrase Quality Evaluator. Replaces both name and qualityRequirements. (PUT /v1/aiChecks/{uid}). 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 bqe_update_ai_check: 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.
bqe_update_ai_check 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 bqe_update_ai_check 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 bqe_update_ai_check. 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.
bqe_update_ai_check 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 →