get_wordpress_settings
Get WordPress settings for a hosting package
This record as markdown: /tools/cbrown35-20i-mcp/get-wordpress-settings.md
What get_wordpress_settings does on 20i MCP Server
AI agents call get_wordpress_settings to retrieve information from 20i 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 get_wordpress_settings is rated Low
This tool retrieves configuration data for WordPress hosted on the 20i platform. It performs no modifications, deletions, or triggering of external operations. The data returned is informational only, making it a Read operation with minimal security risk—disclosure of hosting settings has limited immediate impact and cannot cause service disruption or data loss if misused by an AI agent.
From the tool's definition Tool name is 'get_wordpress_settings' with description 'Get WordPress settings for a hosting package'. The verb 'get' and the absence of any modification language indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_wordpress_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_wordpress_settings, this is the rule to start with:
get_wordpress_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 20i MCP Server, apply this rule, and every get_wordpress_settings call is checked against it from then on.
Questions about get_wordpress_settings
Get WordPress settings for a hosting package. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_wordpress_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 20i MCP Server. Nothing to install.
get_wordpress_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_wordpress_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_wordpress_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_wordpress_settings is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue