update_terms · POEditor MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_terms does on POEditor MCP Server

AI agents use update_terms 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.

WHY IT NEEDS A POLICY

Why update_terms needs a policy

update_terms modifies term metadata reversibly without deleting or destroying data, placing it in the Write category. Severity is medium because misconfiguration could corrupt translation project metadata across multiple languages, affecting translation workflows, but the changes are reversible (can be updated again).

From the tool's definition Tool description states it 'Update[s] term metadata such as the display text, context, references, or tags' and 'Identify each term by its current term/context values'. This is a modification operation that changes existing data (metadata) reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_terms Rate-limited

update_terms stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_terms": {
      "limits": [
        {
          "counter": "update_terms_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches POEditor MCP Server, so you can run agents against it safely.

FAQ

Questions about update_terms

What does the update_terms tool do? +

Update term metadata such as the display text, context, references, or tags. Identify each term by its current term/context values. 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.

How do I enforce a policy on update_terms? +

Register the POEditor MCP Server MCP server in PolicyLayer and add a rule for update_terms: 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.

What risk level is update_terms? +

update_terms is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_terms? +

Yes. Add a rate_limit block to the update_terms 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.

How do I block update_terms completely? +

Set action: deny in the PolicyLayer policy for update_terms. 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.

What MCP server provides update_terms? +

update_terms 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.