AI agents call i18n_validate_keys to retrieve information from Shipeasy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries/validates existing data (whether keys exist in the server-side configuration) without creating, modifying, deleting, or executing operations. It is a read-only verification step that reports drift status via exit code. No side effects occur beyond the check itself.
From the tool's definition Tool performs 'scan code for referenced keys, confirm each exists server-side' — a validation and verification action with no modification, deletion, or execution of external operations. The pre-commit check pattern confirms it is a diagnostic read operation.
Attacks that exploit this kind of access
Pre-commit check — scan code for referenced keys, confirm each exists server-side. Exits non-zero on drift. It is categorised as a Read tool in the Shipeasy MCP Server, which means it retrieves data without modifying state.
Register the Shipeasy MCP server in PolicyLayer and add a rule for i18n_validate_keys: 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_validate_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the i18n_validate_keys 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_validate_keys. 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_validate_keys 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 →