AI agents call get_namespace_keys to retrieve information from I18n without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves metadata about translation keys without accessing sensitive values, modifying data, or triggering external operations. This is a straightforward read operation with minimal risk even if misused by an agent.
From the tool's definition Tool description states it 'Return[s] a sorted list of all dot-notation keys in a namespace (from the primary locale) without their values.' This is purely a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Return a sorted list of all dot-notation keys in a namespace (from the primary locale) without their values. It is categorised as a Read tool in the I18n MCP Server, which means it retrieves data without modifying state.
Register the I18n MCP server in PolicyLayer and add a rule for get_namespace_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 I18n. Nothing to install.
get_namespace_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 get_namespace_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 get_namespace_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.
get_namespace_keys is provided by the I18n MCP server (robin-heat/i18n-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 →