test_saved_external_account

Re-test a saved connected account

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/test-saved-external-account.md

WHAT IT DOES

What test_saved_external_account does on TrekMail MCP Server

AI agents call test_saved_external_account 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 test_saved_external_account is rated Low

The tool appears to re-run a connectivity or validation test against a previously saved external account. Testing/probing is a read-like operation with no apparent side effects on data. However, the description is minimal, so there is some uncertainty about whether the test triggers any state changes on the external account side.

From the tool's definition Re-test a saved connected account

Attacks that exploit this kind of access

RECOMMENDED RULE

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

test_saved_external_account Allowed

test_saved_external_account 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": {
    "test_saved_external_account": {}
  }
}

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 test_saved_external_account call is checked against it from then on.

FAQ

Questions about test_saved_external_account

What does the test_saved_external_account tool do? +

Re-test a saved connected account. 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 test_saved_external_account? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for test_saved_external_account: 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 test_saved_external_account? +

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

Can I rate-limit test_saved_external_account? +

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

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

test_saved_external_account 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

The MCP Attack Database →

Guides

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