Get the settings of the WordPress site. Only admin users have permission to do this.
AI agents call get_site_settings to retrieve information from WordPress 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 configuration data without modifying it, placing it in the Read category. While severity is elevated to medium (rather than low) because site settings often contain sensitive information like API keys, authentication details, email configurations, and other system-critical data that could be exploited if exposed to an unauthorized AI agent, the core action is read-only.
From the tool's definition Tool name and description indicate retrieval of site settings: 'Get the settings of the WordPress site.' No modification, deletion, or execution described. Permission restricted to admin users.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get the settings of the WordPress site. Only admin users have permission to do this. 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 get_site_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.
get_site_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 get_site_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 get_site_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.
get_site_settings is provided by the WordPress MCP Server MCP server (obot-platform/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →