PREFERRED METHOD: Create multiple new terms and add their translations in one operation. Use this instead of calling add_terms followed by add_translations separately. This ensures terms and translations are properly linked (especially important when using context).
AI agents use add_terms_with_translations to create or update resources in POEditor MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your POEditor MCP Server environment.
This tool modifies translation data by creating new terms and translations. While the operations are reversible (terms and translations can be deleted via sibling tools delete_terms and delete_translations), the tool is primarily generative rather than destructive.
From the tool's definition Tool creates new terms and adds translations in a single operation. The description explicitly states it 'Create[s] multiple new terms and add[s] their translations,' which are reversible write operations on translation data.
Attacks that exploit this kind of access
PREFERRED METHOD: Create multiple new terms and add their translations in one operation. Use this instead of calling add_terms followed by add_translations separately. This ensures terms and translations are properly linked (especially important when using context). It is categorised as a Write tool in the POEditor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the POEditor MCP Server MCP server in PolicyLayer and add a rule for add_terms_with_translations: 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 POEditor MCP Server. Nothing to install.
add_terms_with_translations 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 add_terms_with_translations 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 add_terms_with_translations. 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.
add_terms_with_translations is provided by the POEditor MCP Server MCP server (ryan-shaw/poeditor-mcp). 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 →