wpml_get_string_translations
Ruft registrierte String-Übersetzungen ab
This record as markdown: /tools/c-sakel-wp-mcp-server/wpml-get-string-translations.md
What wpml_get_string_translations does on WordPress MCP Server
AI agents call wpml_get_string_translations to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wpml_get_string_translations is rated Low
This tool queries and retrieves existing translation strings from the WPML (WordPress Multilingual Plugin) system. It performs a read-only operation that fetches data without creating, modifying, deleting, or executing anything. The German description confirms it 'retrieves' (Ruft ab) registered translations, which is a pure data retrieval action. No blast radius from misuse as it only exposes existing translations.
From the tool's definition Tool name 'wpml_get_string_translations' and description 'Ruft registrierte String-Übersetzungen ab' (retrieves registered string translations) indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs wpml_get_string_translations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wpml_get_string_translations, this is the rule to start with:
wpml_get_string_translations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every wpml_get_string_translations call is checked against it from then on.
Questions about wpml_get_string_translations
Ruft registrierte String-Übersetzungen ab. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wpml_get_string_translations: 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 WordPress MCP Server. Nothing to install.
wpml_get_string_translations 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 wpml_get_string_translations 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 wpml_get_string_translations. 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.
wpml_get_string_translations is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue