hosting_listAccountCronJobsV1
Returns the list of cron jobs configured for the specified account, including their schedule and command.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-listaccountcronjobsv1.md
What hosting_listAccountCronJobsV1 does on Hostinger Api
AI agents call hosting_listAccountCronJobsV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_listAccountCronJobsV1 is rated Low
This tool queries and retrieves existing cron job configuration data from an account without executing, modifying, or deleting any cron jobs. It is a read-only operation that has no side effects beyond retrieving information.
From the tool's definition Tool name contains 'list' and description states 'Returns the list of cron jobs', indicating data retrieval with no modification or execution of those jobs.
Attacks that exploit this kind of access
The rule that runs hosting_listAccountCronJobsV1 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_listAccountCronJobsV1, this is the rule to start with:
hosting_listAccountCronJobsV1 is read-only, so it stays allowed. 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_listAccountCronJobsV1 call is checked against it from then on.
Questions about hosting_listAccountCronJobsV1
Returns the list of cron jobs configured for the specified account, including their schedule and command. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_listAccountCronJobsV1 accepts 1 parameter: username. Required: 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_listAccountCronJobsV1: 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_listAccountCronJobsV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hosting_listAccountCronJobsV1 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_listAccountCronJobsV1. 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_listAccountCronJobsV1 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