This record as markdown: /tools/hostinger-mcp/agency-cron-delete.md
What agency_cron_delete does on Hostinger
AI agents call agency_cron_delete 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.
Why agency_cron_delete is rated Critical
Deletion of a cron job is an irreversible operation that cannot be undone without manual recreation. Once deleted, the scheduled task is permanently removed from the system. This qualifies as Destructive rather than Write (which is reversible). High severity because deleting critical cron jobs could disrupt automated business processes, backups, or maintenance tasks.
From the tool's definition Tool name is 'agency_cron_delete' and description explicitly states 'Delete a cron job.' The word 'Delete' indicates irreversible removal of data/configuration.
Attacks that exploit this kind of access
The rule that runs agency_cron_delete 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 agency_cron_delete, this is the rule to start with:
agency_cron_delete 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, apply this rule, and every agency_cron_delete call is checked against it from then on.
Questions about agency_cron_delete
Delete a cron job. 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.
Register the Hostinger MCP server in PolicyLayer and add a rule for agency_cron_delete: 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.
agency_cron_delete 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_cron_delete 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_cron_delete. 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_cron_delete 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.
More on Hostinger, and thousands of servers like it.
Across the catalogue