This record as markdown: /tools/hostinger-mcp/mail-logs-access.md
What mail_logs_access does on Hostinger
AI agents call mail_logs_access to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mail_logs_access is rated Low
This tool retrieves historical log data about mail access without creating, modifying, deleting, or executing anything. It is a passive read operation with minimal blast radius—an AI agent could at worst access log information it shouldn't, but cannot alter system state or delete data. Severity is low because log access, while potentially sensitive, does not enable destructive or financial actions.
From the tool's definition Tool name 'mail_logs_access' and description 'List mail access logs' indicate a query/retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs mail_logs_access safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_logs_access, this is the rule to start with:
mail_logs_access 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, apply this rule, and every mail_logs_access call is checked against it from then on.
Questions about mail_logs_access
List mail access logs. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for mail_logs_access: 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. Nothing to install.
mail_logs_access 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 mail_logs_access 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 mail_logs_access. 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.
mail_logs_access is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue