agency-hosting_createAgencyPlanWebsiteCronJobV1
Creates a cron job for an Agency Plan website from a schedule expression and a command. Returns the created cron job, including its uuid, which is required to delete the cron job.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-createagencyplanwebsitecronjobv1.md
What agency-hosting_createAgencyPlanWebsiteCronJobV1 does on Hostinger Api
AI agents use agency-hosting_createAgencyPlanWebsiteCronJobV1 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 (standard 5-field crontab syntax). |
command | string | Yes | Command to run on the schedule. Must not contain pipe (|) or redirection (<, >) characters. |
website_uid | string | Yes | Agency Plan website UID |
Parameters from the server's own tool schema.
Why agency-hosting_createAgencyPlanWebsiteCronJobV1 is rated Medium
An AI agent can call agency-hosting_createAgencyPlanWebsiteCronJobV1 faster than any human can review: one bad instruction and it creates or modifies resources in Hostinger Api by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs agency-hosting_createAgencyPlanWebsiteCronJobV1 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_createAgencyPlanWebsiteCronJobV1, this is the rule to start with:
agency-hosting_createAgencyPlanWebsiteCronJobV1 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 agency-hosting_createAgencyPlanWebsiteCronJobV1 call is checked against it from then on.
Questions about agency-hosting_createAgencyPlanWebsiteCronJobV1
Creates a cron job for an Agency Plan website from a schedule expression and a command. Returns the created cron job, including its uuid, which is required to delete the cron job. 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.
agency-hosting_createAgencyPlanWebsiteCronJobV1 accepts 3 parameters: time, command, website_uid. Required: time, command, 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_createAgencyPlanWebsiteCronJobV1: 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_createAgencyPlanWebsiteCronJobV1 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 agency-hosting_createAgencyPlanWebsiteCronJobV1 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_createAgencyPlanWebsiteCronJobV1. 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_createAgencyPlanWebsiteCronJobV1 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