mail_search_messages
Search email messages across all mailboxes by subject or sender. Returns matches with message IDs usable in mail_read_message. For threaded conversations all message IDs in the thread are returned.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/mail-search-messages.md
What mail_search_messages does on AIquila — Nextcloud MCP Server
AI agents call mail_search_messages to retrieve information from AIquila — Nextcloud MCP Server 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 |
|---|---|---|---|
limit | number | — | Max results (default: 10) |
query | string | Yes | Search query (matches subject and sender name) |
Parameters from the server's own tool schema.
Why mail_search_messages is rated Low
This tool queries and retrieves email data by subject or sender without altering, deleting, or executing anything. It is a search/retrieval function that fits the Read category. Severity is low because email search is a standard, low-risk operation with minimal blast radius — it only exposes what the user already has access to view.
From the tool's definition Tool performs 'Search email messages' and 'Returns matches with message IDs' — purely retrieval of existing data with no modification, deletion, or execution. No side effects beyond querying.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs mail_search_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_search_messages, this is the rule to start with:
mail_search_messages 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 AIquila — Nextcloud MCP Server, apply this rule, and every mail_search_messages call is checked against it from then on.
Questions about mail_search_messages
Search email messages across all mailboxes by subject or sender. Returns matches with message IDs usable in mail_read_message. For threaded conversations all message IDs in the thread are returned. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
mail_search_messages accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for mail_search_messages: 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 AIquila — Nextcloud MCP Server. Nothing to install.
mail_search_messages 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_search_messages 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_search_messages. 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_search_messages is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue