polylang_list_languages
Listet alle konfigurierten Polylang-Sprachen auf
This record as markdown: /tools/c-sakel-wp-mcp-server/polylang-list-languages.md
What polylang_list_languages does on WordPress MCP Server
AI agents call polylang_list_languages 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 polylang_list_languages is rated Low
This tool retrieves configuration metadata about installed languages in a WordPress Polylang setup. It performs a read-only query that returns existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent could only learn what languages are configured, with no ability to alter site state or cause harm.
From the tool's definition Tool name 'polylang_list_languages' and description 'Lists all configured Polylang languages' indicate a query/retrieval operation with no mutation or side effects.
Attacks that exploit this kind of access
The rule that runs polylang_list_languages 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 polylang_list_languages, this is the rule to start with:
polylang_list_languages 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 polylang_list_languages call is checked against it from then on.
Questions about polylang_list_languages
Listet alle konfigurierten Polylang-Sprachen auf. 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 polylang_list_languages: 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.
polylang_list_languages 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 polylang_list_languages 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 polylang_list_languages. 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.
polylang_list_languages 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