update_namespace · Tolgee MCP: Risk & Policy

WHAT IT DOES

What update_namespace does on Tolgee

AI agents use update_namespace to create or update resources in Tolgee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tolgee environment.

WHY IT NEEDS A POLICY

Why update_namespace needs a policy

The tool updates/modifies project structure (namespace name) without irreversible deletion. Renaming is categorized as Write because it creates or modifies data reversibly. Severity is medium because misuse could disrupt translation workflows and require correction, but the operation is non-destructive and localized to namespace metadata within a single project.

From the tool's definition Tool description states 'Rename a namespace' — this modifies metadata within a Tolgee project. Renaming is a reversible write operation that does not delete or permanently destroy data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_namespace Rate-limited

update_namespace 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_namespace": {
      "limits": [
        {
          "counter": "update_namespace_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 Tolgee, so you can run agents against it safely.

FAQ

Questions about update_namespace

What does the update_namespace tool do? +

Rename a namespace in a Tolgee project. It is categorised as a Write tool in the Tolgee 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_namespace? +

Register the Tolgee MCP server in PolicyLayer and add a rule for update_namespace: 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 Tolgee. Nothing to install.

What risk level is update_namespace? +

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

Can I rate-limit update_namespace? +

Yes. Add a rate_limit block to the update_namespace 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_namespace completely? +

Set action: deny in the PolicyLayer policy for update_namespace. 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_namespace? +

update_namespace is provided by the Tolgee MCP server (ytarfa/tolgee-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.