hosting_getNode_jsRuntimeLogsV1
Returns the Node.js application's runtime console log entries, oldest first, each with timestamp, level and message. On the first call send period (1h, 1d, 1w or 1m) and optionally levels and limit (1-5000, default 1000); when more entries match than limit, the newest are kept. To poll for new en...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-getnode-jsruntimelogsv1.md
What hosting_getNode_jsRuntimeLogsV1 does on Hostinger Api
AI agents call hosting_getNode_jsRuntimeLogsV1 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 |
|---|---|---|---|
limit | integer | — | Maximum number of log entries to return. When more entries match, the newest are kept. |
domain | string | Yes | Domain name |
levels | array | — | Return only entries with these log levels, sent as a comma-separated list, e.g. ERROR,WARN. Matching runs on the raw log line, so entries written with numeric l |
period | string | — | Time window for the first fetch. Required when `from_line` is not sent. |
username | string | Yes | username parameter |
from_line | integer | — | 1-based line of the log file to start from. For polling send `total_lines + 1` from the previous response. Cannot be combined with `period`. |
Parameters from the server's own tool schema.
Why hosting_getNode_jsRuntimeLogsV1 is rated Low
Tool retrieves application logs without side effects or data modification capabilities.
From the tool's definition Returns Node.js runtime console log entries; read-only retrieval, no modifications.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs hosting_getNode_jsRuntimeLogsV1 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_getNode_jsRuntimeLogsV1, this is the rule to start with:
hosting_getNode_jsRuntimeLogsV1 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_getNode_jsRuntimeLogsV1 call is checked against it from then on.
Questions about hosting_getNode_jsRuntimeLogsV1
Returns the Node.js application's runtime console log entries, oldest first, each with timestamp, level and message. On the first call send period (1h, 1d, 1w or 1m) and optionally levels and limit (1-5000, default 1000); when more entries match than limit, the newest are kept. To poll for new entries send total_lines + 1 from the previous response as from_line and omit period; period and from_line cannot be combined. Lines that are not JSON with a timestamp, level and message are skipped, so logs may hold fewer than limit entries while total_lines counts every raw line. Entries with a timestamp before last_deployed_at belong to the previous deployment. Returns an empty logs list when the application has not written a log file yet. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_getNode_jsRuntimeLogsV1 accepts 6 parameters: limit, domain, levels, period, username, from_line. Required: domain, 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_getNode_jsRuntimeLogsV1: 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_getNode_jsRuntimeLogsV1 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_getNode_jsRuntimeLogsV1 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_getNode_jsRuntimeLogsV1. 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_getNode_jsRuntimeLogsV1 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