i18n_publish_profile · Shipeasy MCP: Risk & Policy

WHAT IT DOES

What i18n_publish_profile does on Shipeasy

AI agents invoke i18n_publish_profile to trigger actions in Shipeasy. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why i18n_publish_profile needs a policy

This tool executes external operations: rebuilding a KV manifest and purging CDN caches. These are not simple writes — they actively modify distributed infrastructure state and invalidate cached content globally. A CDN purge is a significant operational action with wide blast radius (can disrupt live users if done incorrectly), placing this firmly in Execute.

From the tool's definition "rebuild KV manifest + purge CDN" — triggers external operations (CDN purge and KV manifest rebuild) that affect production infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

i18n_publish_profile Rate-limited

i18n_publish_profile stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "i18n_publish_profile": {
      "limits": [
        {
          "counter": "i18n_publish_profile_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about i18n_publish_profile

What does the i18n_publish_profile tool do? +

Publish a chunk or whole profile: rebuild KV manifest + purge CDN. It is categorised as a Execute tool in the Shipeasy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on i18n_publish_profile? +

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

What risk level is i18n_publish_profile? +

i18n_publish_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit i18n_publish_profile? +

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

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

i18n_publish_profile is provided by the Shipeasy MCP server (shipeasy-ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.