list_mailboxes_v1
Возвращает все почтовые ящики аккаунта в формате API v1 (с полной детализацией auto_reply/spam_filter/forwarding). Предпочитай list_mailboxes (v2), этот нужен только если требуются v1-поля.
This record as markdown: /tools/timeweb-mcp/list-mailboxes-v1.md
What list_mailboxes_v1 does on Timeweb
AI agents call list_mailboxes_v1 to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_mailboxes_v1 is rated Low
Even though list_mailboxes_v1 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.
Attacks that exploit this kind of access
The rule that runs list_mailboxes_v1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_mailboxes_v1, this is the rule to start with:
list_mailboxes_v1 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 Timeweb, apply this rule, and every list_mailboxes_v1 call is checked against it from then on.
Questions about list_mailboxes_v1
Возвращает все почтовые ящики аккаунта в формате API v1 (с полной детализацией auto_reply/spam_filter/forwarding). Предпочитай list_mailboxes (v2), этот нужен только если требуются v1-поля. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
Register the Timeweb MCP server in PolicyLayer and add a rule for list_mailboxes_v1: 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 Timeweb. Nothing to install.
list_mailboxes_v1 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 list_mailboxes_v1 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 list_mailboxes_v1. 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.
list_mailboxes_v1 is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue