get_sieve_script

Get the current Sieve script for a mailbox. Returns the auto-generated script built from visual filters and auto-reply settings. Use this to inspect what is running on the server.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/get-sieve-script.md

WHAT IT DOES

What get_sieve_script does on TrekMail MCP Server

AI agents call get_sieve_script to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_sieve_script is rated Low

This tool retrieves and queries the current Sieve script configuration for a mailbox without modifying, executing, or deleting any data. It is purely informational inspection of existing infrastructure state. The low severity reflects minimal blast radius even if misused by an agent, as it only exposes script contents without the ability to modify, execute, or delete them.

From the tool's definition Tool name 'get_sieve_script' and description 'Get the current Sieve script for a mailbox. Returns the auto-generated script...' - uses 'Get' verb and returns/retrieves data with 'no side effects' as stated in the description ('inspect what is running').

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_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 get_sieve_script, this is the rule to start with:

get_sieve_script Allowed

get_sieve_script is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_sieve_script": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every get_sieve_script call is checked against it from then on.

FAQ

Questions about get_sieve_script

What does the get_sieve_script tool do? +

Get the current Sieve script for a mailbox. Returns the auto-generated script built from visual filters and auto-reply settings. Use this to inspect what is running on the server. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_sieve_script? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_sieve_script? +

get_sieve_script is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_sieve_script? +

Yes. Add a rate_limit block to the get_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.

How do I block get_sieve_script completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_sieve_script? +

get_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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →