polylang_get_post_language
Ruft die Sprache eines Posts und seine Übersetzungen ab
This record as markdown: /tools/c-sakel-wp-mcp-server/polylang-get-post-language.md
What polylang_get_post_language does on WordPress MCP Server
AI agents call polylang_get_post_language 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_get_post_language is rated Low
This tool retrieves (gets) language and translation information for a WordPress post without modifying, deleting, or executing operations. It is a read-only query operation with no side effects, fitting the 'Read' category. The blast radius is minimal—exposing language metadata poses no security or operational risk.
From the tool's definition Tool name 'polylang_get_post_language' and description 'Ruft die Sprache eines Posts und seine Übersetzungen ab' (retrieves the language of a post and its translations) indicates a query operation that fetches metadata about post language and translation…
Attacks that exploit this kind of access
The rule that runs polylang_get_post_language 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_get_post_language, this is the rule to start with:
polylang_get_post_language 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_get_post_language call is checked against it from then on.
Questions about polylang_get_post_language
Ruft die Sprache eines Posts und seine Ü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 polylang_get_post_language: 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_get_post_language 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_get_post_language 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_get_post_language. 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_get_post_language 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