hosting_getWebsiteFileContentV1
Get a single file's content, relative to a website's document root. Read-only; refuses symlinks, oversized files, non-text file types, and files identified as containing secrets (e.g. credential files) — none of these are returned by this endpoint.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-getwebsitefilecontentv1.md
What hosting_getWebsiteFileContentV1 does on Hostinger Api
AI agents call hosting_getWebsiteFileContentV1 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 |
|---|---|---|---|
path | string | Yes | File path, relative to the document root. |
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
from_line | integer | — | Line offset to start reading from. |
max_lines | integer | — | Max number of lines to return. |
Parameters from the server's own tool schema.
Why hosting_getWebsiteFileContentV1 is rated Low
Retrieves file content with explicit safeguards; no side effects or data modification.
From the tool's definition Get a single file's content, read-only, refuses symlinks, oversized files, non-text.
Risk signalsAccepts file system path (path) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs hosting_getWebsiteFileContentV1 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_getWebsiteFileContentV1, this is the rule to start with:
hosting_getWebsiteFileContentV1 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_getWebsiteFileContentV1 call is checked against it from then on.
Questions about hosting_getWebsiteFileContentV1
Get a single file's content, relative to a website's document root. Read-only; refuses symlinks, oversized files, non-text file types, and files identified as containing secrets (e.g. credential files) — none of these are returned by this endpoint. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_getWebsiteFileContentV1 accepts 5 parameters: path, domain, username, from_line, max_lines. Required: path, 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_getWebsiteFileContentV1: 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_getWebsiteFileContentV1 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_getWebsiteFileContentV1 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_getWebsiteFileContentV1. 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_getWebsiteFileContentV1 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