agency-hosting_deleteAgencyPlanWebsiteCronJobV1
Permanently deletes the cron job identified by its uuid from an Agency Plan website. The operation is idempotent: deleting a cron job that does not exist succeeds without error.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deleteagencyplanwebsitecronjobv1.md
What agency-hosting_deleteAgencyPlanWebsiteCronJobV1 does on Hostinger Api
AI agents call agency-hosting_deleteAgencyPlanWebsiteCronJobV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
uuid | string | Yes | Unique identifier of the cron job as returned by the list cron jobs endpoint. |
website_uid | string | Yes | Agency Plan website UID |
Parameters from the server's own tool schema.
Why agency-hosting_deleteAgencyPlanWebsiteCronJobV1 is rated Critical
An AI agent that decides to call agency-hosting_deleteAgencyPlanWebsiteCronJobV1 doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hostinger Api is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs agency-hosting_deleteAgencyPlanWebsiteCronJobV1 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 agency-hosting_deleteAgencyPlanWebsiteCronJobV1, this is the rule to start with:
agency-hosting_deleteAgencyPlanWebsiteCronJobV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every agency-hosting_deleteAgencyPlanWebsiteCronJobV1 call is checked against it from then on.
Questions about agency-hosting_deleteAgencyPlanWebsiteCronJobV1
Permanently deletes the cron job identified by its uuid from an Agency Plan website. The operation is idempotent: deleting a cron job that does not exist succeeds without error. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
agency-hosting_deleteAgencyPlanWebsiteCronJobV1 accepts 2 parameters: uuid, website_uid. Required: uuid, website_uid. 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 agency-hosting_deleteAgencyPlanWebsiteCronJobV1: 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.
agency-hosting_deleteAgencyPlanWebsiteCronJobV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the agency-hosting_deleteAgencyPlanWebsiteCronJobV1 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 agency-hosting_deleteAgencyPlanWebsiteCronJobV1. 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.
agency-hosting_deleteAgencyPlanWebsiteCronJobV1 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.
Across the catalogue