rename_message · Paraglide MCP: Risk & Policy

WHAT IT DOES

What rename_message does on Paraglide

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

WHY IT NEEDS A POLICY

Why rename_message needs a policy

This tool creates or modifies data reversibly by renaming keys in a translation system. While it affects multiple locales, the operation is reversible (can be renamed back) and does not delete data or trigger external code execution. It is categorized as Write rather than Destructive because the underlying translation content is preserved and the action can be undone.

From the tool's definition Tool 'rename_message' modifies message keys across all locales while preserving translated values. The description states it will 'rename a message key across every locale', which is a data modification operation.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_message Rate-limited

rename_message 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": {
    "rename_message": {
      "limits": [
        {
          "counter": "rename_message_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 Paraglide, so you can run agents against it safely.

FAQ

Questions about rename_message

What does the rename_message tool do? +

Rename a message key across every locale, keeping all translated values. It is categorised as a Write tool in the Paraglide MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_message? +

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

What risk level is rename_message? +

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

Can I rate-limit rename_message? +

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

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

rename_message is provided by the Paraglide MCP server (weshaze/paraglide-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.