clear_api_cache

Clear the internal response cache. Use when you need fresh data after making changes.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What clear_api_cache does on Hostinger

AI agents call clear_api_cache to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clear_api_cache is rated Critical

Clearing a cache is an irreversible action that destroys cached data. While the underlying source data is not lost, the cached responses are permanently removed and cannot be undone. Severity is medium because the blast radius is limited — it forces re-fetching from the source but does not destroy primary data, and the main risk is temporary performance degradation or stale-data issues being exposed.

From the tool's definition Clear the internal response cache

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clear_api_cache Hidden

clear_api_cache is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_api_cache"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about clear_api_cache

What does the clear_api_cache tool do? +

Clear the internal response cache. Use when you need fresh data after making changes. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_api_cache? +

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

clear_api_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_api_cache? +

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

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

clear_api_cache 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 → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →