admin_get_settings
Ruft WordPress Site-Einstellungen ab (Titel, Beschreibung, Zeitzone, etc.)
This record as markdown: /tools/c-sakel-wp-mcp-server/admin-get-settings.md
What admin_get_settings does on WordPress MCP Server
AI agents call admin_get_settings 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 admin_get_settings is rated Low
This tool retrieves configuration metadata about a WordPress site without modifying, executing, or destroying anything. It is a read-only query operation with minimal blast radius—exposure of basic site settings poses low risk compared to tools that can modify content or execute code. The German description 'Ruft WordPress Site-Einstellungen ab' confirms it fetches/retrieves settings only.
From the tool's definition Tool name contains 'get' and description states 'Ruft...ab' (retrieves/fetches) WordPress site settings (title, description, timezone, etc.) with no mention of modification, deletion, or execution of external operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin_get_settings 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 admin_get_settings, this is the rule to start with:
admin_get_settings 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 admin_get_settings call is checked against it from then on.
Questions about admin_get_settings
Ruft WordPress Site-Einstellungen ab (Titel, Beschreibung, Zeitzone, etc.). 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 admin_get_settings: 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.
admin_get_settings 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 admin_get_settings 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 admin_get_settings. 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.
admin_get_settings 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