hosting_createAccountCronJobV1
Creates a cron job for the specified account from a schedule expression and a command. Returns the created cron job, including its uid, which is required to delete the cron job or fetch its output.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-createaccountcronjobv1.md
What hosting_createAccountCronJobV1 does on Hostinger Api
AI agents use hosting_createAccountCronJobV1 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 |
|---|---|---|---|
time | string | Yes | Cron schedule expression (for example "0 2 * * *" runs daily at 02:00). |
command | string | Yes | Command to execute on the schedule. |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_createAccountCronJobV1 is rated Medium
This tool creates a new cron job resource, which is a reversible write operation (the cron job can be deleted later using its uid). However, the cron job itself executes arbitrary commands on a schedule, so misuse could lead to repeated execution of harmful commands. The act of creation itself is Write, not Execute, but the medium severity reflects the indirect execution risk.
From the tool's definition Creates a cron job for the specified account from a schedule expression and a command
Attacks that exploit this kind of access
The rule that runs hosting_createAccountCronJobV1 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_createAccountCronJobV1, this is the rule to start with:
hosting_createAccountCronJobV1 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_createAccountCronJobV1 call is checked against it from then on.
Questions about hosting_createAccountCronJobV1
Creates a cron job for the specified account from a schedule expression and a command. Returns the created cron job, including its uid, which is required to delete the cron job or fetch its output. 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_createAccountCronJobV1 accepts 3 parameters: time, command, username. Required: time, command, 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_createAccountCronJobV1: 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_createAccountCronJobV1 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_createAccountCronJobV1 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_createAccountCronJobV1. 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_createAccountCronJobV1 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