Retrieves authoritative documentation for i18n libraries (currently react-intl). When to Use Called during i18n_checklist Steps 7-10. The checklist tool will tell you when you need i18n library documentation. Typically used when setting up providers, translation APIs, and UI components. If you're...
Part of the Main server.
Free to start. No card required.
AI agents call get_i18n_library_docs to retrieve information from Main without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_i18n_library_docs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_i18n_library_docs": {}
}
}See the full Main policy for all 4 tools.
These attack patterns abuse exactly the kind of access get_i18n_library_docs gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Retrieves authoritative documentation for i18n libraries (currently react-intl). When to Use Called during i18n_checklist Steps 7-10. The checklist tool will tell you when you need i18n library documentation. Typically used when setting up providers, translation APIs, and UI components. If you're implementing i18n: Let the checklist guide you. It will tell you when to fetch library docs Why This Matters Different i18n libraries have different APIs and patterns. Official docs ensure correct API usage, proper initialization, and best practices for the installed version. How to Use Two-Phase Workflow: 1. Discovery - Call with action="index" 2. Reading - Call with action="read" and section_id Parameters: - library: Currently only "react-intl" supported - version: Use "latest" - action: "index" or "read" - section_id: Required for action="read" Example: get_i18n_library_docs(library="react-intl", action="index") get_i18n_library_docs(library="react-intl", action="read", section_id="0:3") What You Get - Index: Available documentation sections - Read: Full API references and usage examples. It is categorised as a Read tool in the Main MCP Server, which means it retrieves data without modifying state.
Register the Main MCP server in PolicyLayer and add a rule for get_i18n_library_docs: 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 Main. Nothing to install.
get_i18n_library_docs 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_i18n_library_docs 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_i18n_library_docs. 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_i18n_library_docs is provided by the Main MCP server (https://mcp.lingo.dev/main). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Main tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.