hosting_deleteAccountCronJobV1
Permanently deletes the cron job identified by its uid. The uid is returned by the list cron jobs endpoint.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountcronjobv1.md
What hosting_deleteAccountCronJobV1 does on Hostinger Api
AI agents call hosting_deleteAccountCronJobV1 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 |
|---|---|---|---|
uid | string | Yes | Unique identifier of the cron job as returned by the list cron jobs endpoint. |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_deleteAccountCronJobV1 is rated Critical
The tool explicitly performs an irreversible deletion operation ('Permanently deletes') on a cron job resource. This is a destructive action that cannot be undone, matching the Destructive category definition. The severity is high because deletion of cron jobs could disrupt critical scheduled tasks and business operations, though the blast radius is limited to a single cron job rather than broader system-wide data.
From the tool's definition Permanently deletes the cron job identified by its uid
Attacks that exploit this kind of access
The rule that runs hosting_deleteAccountCronJobV1 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_deleteAccountCronJobV1, this is the rule to start with:
hosting_deleteAccountCronJobV1 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 hosting_deleteAccountCronJobV1 call is checked against it from then on.
Questions about hosting_deleteAccountCronJobV1
Permanently deletes the cron job identified by its uid. The uid is returned by the list cron jobs endpoint. 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.
hosting_deleteAccountCronJobV1 accepts 2 parameters: uid, username. Required: uid, 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_deleteAccountCronJobV1: 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_deleteAccountCronJobV1 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 hosting_deleteAccountCronJobV1 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_deleteAccountCronJobV1. 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_deleteAccountCronJobV1 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