hosting_getCronJobOutputV1
Returns the output captured from the last execution of 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-getcronjoboutputv1.md
What hosting_getCronJobOutputV1 does on Hostinger Api
AI agents call hosting_getCronJobOutputV1 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 |
|---|---|---|---|
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_getCronJobOutputV1 is rated Low
This tool retrieves historical cron job execution output. It does not modify, delete, execute, or trigger any actions — it merely fetches and displays data that has already been generated. This is a classic Read operation with minimal blast radius if misused, as it can only expose information about past cron executions.
From the tool's definition Tool description states it 'Returns the output captured from the last execution' — a retrieval operation with no side effects. The verb 'Returns' and 'captured from' indicate query-only behavior.
Attacks that exploit this kind of access
The rule that runs hosting_getCronJobOutputV1 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_getCronJobOutputV1, this is the rule to start with:
hosting_getCronJobOutputV1 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_getCronJobOutputV1 call is checked against it from then on.
Questions about hosting_getCronJobOutputV1
Returns the output captured from the last execution of the cron job identified by its uid. The uid is returned by the list cron jobs endpoint. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_getCronJobOutputV1 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_getCronJobOutputV1: 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_getCronJobOutputV1 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_getCronJobOutputV1 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_getCronJobOutputV1. 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_getCronJobOutputV1 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