mail_listActionLogsV1
Retrieve paginated account action logs (administrative and user actions) for the given mail order. Supports filtering by account, date range, and status. Results are sorted by timestamp descending.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-listactionlogsv1.md
What mail_listActionLogsV1 does on Hostinger Api
AI agents call mail_listActionLogsV1 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 |
|---|---|---|---|
date | string | — | Exact date filter (YYYY-MM-DD). Takes precedence over `from_date`/`to_date` when both are given. |
page | integer | — | Page number |
status | string | — | Filter log entries by status |
account | string | — | Filter log entries by a specific email account |
orderId | string | Yes | Order resource ID |
to_date | string | — | Date range end (RFC 3339) |
per_page | integer | — | Number of items per page |
from_date | string | — | Date range start (RFC 3339) |
Parameters from the server's own tool schema.
Why mail_listActionLogsV1 is rated Low
Even though mail_listActionLogsV1 only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs mail_listActionLogsV1 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 mail_listActionLogsV1, this is the rule to start with:
mail_listActionLogsV1 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 mail_listActionLogsV1 call is checked against it from then on.
Questions about mail_listActionLogsV1
Retrieve paginated account action logs (administrative and user actions) for the given mail order. Supports filtering by account, date range, and status. Results are sorted by timestamp descending. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
mail_listActionLogsV1 accepts 8 parameters: date, page, status, account, orderId, to_date, per_page, from_date. Required: orderId. 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 mail_listActionLogsV1: 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.
mail_listActionLogsV1 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_listActionLogsV1 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_listActionLogsV1. 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_listActionLogsV1 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