upload_sieve_script
Upload and activate a custom Sieve script for a mailbox. This replaces any visual filters. The server validates syntax before activating. Agency plan only. Dangerous extensions (vnd.dovecot.pipe, vnd.dovecot.execute, vnd.dovecot.filter) are blocked.
This record as markdown: /tools/trekmail-mcp-server/upload-sieve-script.md
What upload_sieve_script does on TrekMail MCP Server
AI agents invoke upload_sieve_script to trigger actions in TrekMail MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why upload_sieve_script is rated High
Sieve scripts are executable programs that run server-side to filter, redirect, or manipulate email. Uploading and activating one constitutes running code on the mail server. It also irreversibly replaces existing visual filters, though the script itself can be overwritten again.
From the tool's definition 'Upload and activate a custom Sieve script for a mailbox. This replaces any visual filters.' — uploads and activates executable mail-filtering logic; 'The server validates syntax before activating' confirms code execution path.
Attacks that exploit this kind of access
The rule that runs upload_sieve_script safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_sieve_script, this is the rule to start with:
upload_sieve_script stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every upload_sieve_script call is checked against it from then on.
Questions about upload_sieve_script
Upload and activate a custom Sieve script for a mailbox. This replaces any visual filters. The server validates syntax before activating. Agency plan only. Dangerous extensions (vnd.dovecot.pipe, vnd.dovecot.execute, vnd.dovecot.filter) are blocked. It is categorised as a Execute tool in the TrekMail MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for upload_sieve_script: 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 TrekMail MCP Server. Nothing to install.
upload_sieve_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the upload_sieve_script 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 upload_sieve_script. 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.
upload_sieve_script is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
Across the catalogue