Low Risk

get_mail

get_mail

How to control get_mail ↓

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

Low Risk

The tool name 'get_mail' clearly indicates data retrieval from a mailbox with no modification or side effects. The presence of 'del_mail' as a distinct sibling tool confirms that mail deletion is handled separately, so 'get_mail' performs only query/retrieval operations typical of the Read category.

From the tool's definition Tool name 'get_mail' indicates retrieval of mailbox contents; sibling context shows 'del_mail' as a separate destructive operation, implying 'get_mail' is read-only. Description is empty, limiting confidence.

Documented attack patterns abuse exactly the kind of access get_mail gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PTT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_mail:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_mail": {}
  }
}

get_mail is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PTT MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_mail tool do? +

get_mail. It is categorised as a Read tool in the PTT MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_mail? +

Register the PTT MCP Server MCP server in PolicyLayer and add a rule for get_mail: 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 PTT MCP Server. Nothing to install.

What risk level is get_mail? +

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

Can I rate-limit get_mail? +

Yes. Add a rate_limit block to the get_mail 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_mail completely? +

Set action: deny in the PolicyLayer policy for get_mail. 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_mail? +

get_mail is provided by the PTT MCP Server MCP server (pyptt/ptt_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PTT MCP Server tool call.

Deterministic rules across all 26 PTT MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 PTT MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.