hosting_clearNode_jsRuntimeLogsV1
Empties the Node.js application's runtime log file. This cannot be undone, so confirm with the user before calling it. Returns success even when no log file exists yet. Use it before reproducing a problem so the next Get Node.js runtime logs call returns only fresh entries; start that call with p...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-clearnode-jsruntimelogsv1.md
What hosting_clearNode_jsRuntimeLogsV1 does on Hostinger Api
AI agents call hosting_clearNode_jsRuntimeLogsV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_clearNode_jsRuntimeLogsV1 is rated Critical
Irreversibly deletes log data that cannot be recovered or restored afterward.
From the tool's definition Empties the Node.js application's runtime log file. This cannot be undone
Attacks that exploit this kind of access
The rule that runs hosting_clearNode_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_clearNode_jsRuntimeLogsV1, this is the rule to start with:
hosting_clearNode_jsRuntimeLogsV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_clearNode_jsRuntimeLogsV1 call is checked against it from then on.
Questions about hosting_clearNode_jsRuntimeLogsV1
Empties the Node.js application's runtime log file. This cannot be undone, so confirm with the user before calling it. Returns success even when no log file exists yet. Use it before reproducing a problem so the next Get Node.js runtime logs call returns only fresh entries; start that call with period again instead of reusing a from_line from before the clear. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
hosting_clearNode_jsRuntimeLogsV1 accepts 2 parameters: domain, username. 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_clearNode_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_clearNode_jsRuntimeLogsV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hosting_clearNode_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_clearNode_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_clearNode_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.
Across the catalogue