hosting_cache_clear

Clear cache for a hosted website.

SERVERHostinger SOURCEidugeni/hostinger-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/hosting-cache-clear.md

WHAT IT DOES

What hosting_cache_clear does on Hostinger

AI agents invoke hosting_cache_clear to trigger actions in Hostinger. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why hosting_cache_clear is rated High

Clearing a cache is an operational action that triggers an external side effect on the hosting infrastructure. It is not a simple read, and while it modifies the state of the cache, it is not a traditional write/create/update of persistent data. Cache clearing is an execution-type operation that affects website performance and behavior.

From the tool's definition "Clear cache for a hosted website"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_cache_clear 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 hosting_cache_clear, this is the rule to start with:

hosting_cache_clear Rate-limited

hosting_cache_clear stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hosting_cache_clear": {
      "limits": [
        {
          "counter": "hosting_cache_clear_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about hosting_cache_clear

What does the hosting_cache_clear tool do? +

Clear cache for a hosted website. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hosting_cache_clear? +

Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_cache_clear: 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 hosting_cache_clear? +

hosting_cache_clear is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hosting_cache_clear? +

Yes. Add a rate_limit block to the hosting_cache_clear 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 hosting_cache_clear completely? +

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

hosting_cache_clear 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →