Find all translations for a specific key across all components and languages in a project
AI agents call findTranslationsForKey to retrieve information from Weblate MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves translation data without modifying, deleting, or executing any operations. It performs a search query across translations in a project, which is a non-destructive read operation with minimal security risk even if misused by an AI agent.
From the tool's definition Tool name contains 'find' and description states 'Find all translations for a specific key' with no mention of modification, deletion, or execution capabilities. The verb 'find' and the retrieval-only nature align with query/search operations.
Documented attack patterns abuse exactly the kind of access findTranslationsForKey gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weblate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for findTranslationsForKey:
{
"version": "1",
"default": "deny",
"tools": {
"findTranslationsForKey": {}
}
} findTranslationsForKey is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find all translations for a specific key across all components and languages in a project. It is categorised as a Read tool in the Weblate MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weblate MCP Server MCP server in PolicyLayer and add a rule for findTranslationsForKey: 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 Weblate MCP Server. Nothing to install.
findTranslationsForKey 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 findTranslationsForKey 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 findTranslationsForKey. 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.
findTranslationsForKey is provided by the Weblate MCP Server MCP server (mmntm/weblate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weblate MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Weblate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.