AI agents call i1n_check to retrieve information from I1n without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
i1n_check performs static analysis and validation of existing translation files, producing a report of quality metrics (missing keys, broken placeholders, empty values, coverage). It does not create, modify, delete, or execute external operations—only reads and analyzes. This is a classic Read category tool.
From the tool's definition Tool description states it 'Validate[s] local translation files offline' and 'Returns a JSON report.' Key phrases: 'validate', 'offline', 'no API calls' indicate read-only inspection with no side effects.
Attacks that exploit this kind of access
Validate local translation files offline: missing keys per language, broken interpolation placeholders, empty values, and coverage. Returns a JSON report. Safe for CI — no API calls. It is categorised as a Read tool in the I1n MCP Server, which means it retrieves data without modifying state.
Register the I1n MCP server in PolicyLayer and add a rule for i1n_check: 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 I1n. Nothing to install.
i1n_check 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 i1n_check 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 i1n_check. 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.
i1n_check is provided by the I1n MCP server (pakvothe/i1n-cli). 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 →