Add a term to a project
AI agents use add_term 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 creates new translation terms (source strings) within a POEditor project. While this is reversible (terms can be deleted via delete_term), it modifies the project's content structure. It falls under Write category as it creates/adds data without executing arbitrary code or causing irreversible system changes.
From the tool's definition Tool name 'add_term' and description 'Add a term to a project' indicate creation of new data within a translation management system.
Attacks that exploit this kind of access
Add a term to a project. 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_term: 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_term 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_term 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_term. 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_term is provided by the POEditor MCP Server MCP server (r-pedraza/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 →