AI agents use i18n_codemod_apply to create or update resources in Shipeasy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shipeasy environment.
This tool creates or modifies code files through codemod application. While the safeguard (confirm: true) reduces risk, the tool itself performs Write operations that transform source code. It is reversible (unlike Destructive), does not execute arbitrary code in the runtime sense (Execute), and has no financial impact.
From the tool's definition Tool description states 'Apply a previously-previewed codemod' and 'writes' code modifications. Codemods modify source code files, which is a reversible but significant write operation affecting application source.
Attacks that exploit this kind of access
Apply a previously-previewed codemod. Requires confirm: true — never writes without explicit consent from the caller. It is categorised as a Write tool in the Shipeasy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shipeasy MCP server in PolicyLayer and add a rule for i18n_codemod_apply: 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.
i18n_codemod_apply 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 i18n_codemod_apply 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 i18n_codemod_apply. 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.
i18n_codemod_apply 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.
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 →