agency_wp_settings

Get WordPress settings for an Agency Plan website.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/agency-wp-settings.md

WHAT IT DOES

What agency_wp_settings does on Hostinger

AI agents call agency_wp_settings to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why agency_wp_settings is rated Low

This tool retrieves WordPress configuration data for read-only purposes. It has no side effects and does not modify, execute, or delete anything. The blast radius of misuse is minimal—an attacker would only gain visibility into WordPress settings, not control or data destruction.

From the tool's definition Tool name 'agency_wp_settings' and description 'Get WordPress settings for an Agency Plan website' indicate a retrieval operation ('Get'). No modification, deletion, or execution is described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agency_wp_settings safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agency_wp_settings, this is the rule to start with:

agency_wp_settings Allowed

agency_wp_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "agency_wp_settings": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every agency_wp_settings call is checked against it from then on.

FAQ

Questions about agency_wp_settings

What does the agency_wp_settings tool do? +

Get WordPress settings for an Agency Plan website. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on agency_wp_settings? +

Register the Hostinger MCP server in PolicyLayer and add a rule for agency_wp_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 Hostinger. Nothing to install.

What risk level is agency_wp_settings? +

agency_wp_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit agency_wp_settings? +

Yes. Add a rate_limit block to the agency_wp_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.

How do I block agency_wp_settings completely? +

Set action: deny in the PolicyLayer policy for agency_wp_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.

What MCP server provides agency_wp_settings? +

agency_wp_settings is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →