hosting_toggleWebsiteCacheV1
Turns server-side caching for the website on or off, based on the enabled flag. Enable it for faster page loads, reduced server load, and improved user experience; recommended for production websites. Disabling may impact performance; to temporarily bypass caching while developing or debugging, p...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-togglewebsitecachev1.md
What hosting_toggleWebsiteCacheV1 does on Hostinger Api
AI agents use hosting_toggleWebsiteCacheV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
enabled | boolean | Yes | Turn server-side caching on (true) or off (false) for the website. |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_toggleWebsiteCacheV1 is rated Medium
This tool modifies a website configuration setting (server-side caching enabled/disabled). It is reversible (can be toggled back), so it falls under Write rather than Destructive. Misuse could degrade website performance (e.g., disabling caching on a production site), warranting medium severity.
From the tool's definition Turns server-side caching for the website on or off, based on the enabled flag. Does nothing if caching is already in the requested state.
Attacks that exploit this kind of access
The rule that runs hosting_toggleWebsiteCacheV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_toggleWebsiteCacheV1, this is the rule to start with:
hosting_toggleWebsiteCacheV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_toggleWebsiteCacheV1 call is checked against it from then on.
Questions about hosting_toggleWebsiteCacheV1
Turns server-side caching for the website on or off, based on the enabled flag. Enable it for faster page loads, reduced server load, and improved user experience; recommended for production websites. Disabling may impact performance; to temporarily bypass caching while developing or debugging, prefer toggling cacheless mode instead. Does nothing if caching is already in the requested state. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hosting_toggleWebsiteCacheV1 accepts 3 parameters: domain, enabled, username. Required: domain, enabled, username. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_toggleWebsiteCacheV1: 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 Api. Nothing to install.
hosting_toggleWebsiteCacheV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hosting_toggleWebsiteCacheV1 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 hosting_toggleWebsiteCacheV1. 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.
hosting_toggleWebsiteCacheV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue