update_bulk_migration_job_password · TrekMail MCP Server MCP

WHAT IT DOES

What update_bulk_migration_job_password does on TrekMail MCP Server

AI agents use update_bulk_migration_job_password to create or update resources in TrekMail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.

WHY IT NEEDS A POLICY

Why update_bulk_migration_job_password needs a policy

This tool updates (modifies) a stored IMAP password credential, which is a Write operation as it reversibly changes configuration data. Severity is high because compromised or incorrectly configured credentials could cause mail migration failures, data loss, or security exposure, with blast radius across email infrastructure operations.

From the tool's definition Tool name includes 'update' and description states 'Update the source IMAP password for a failed job in a bulk migration batch'. The tool modifies authentication credentials for email migration operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_bulk_migration_job_password Rate-limited

update_bulk_migration_job_password stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_bulk_migration_job_password": {
      "limits": [
        {
          "counter": "update_bulk_migration_job_password_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about update_bulk_migration_job_password

What does the update_bulk_migration_job_password tool do? +

Update the source IMAP password for a failed job in a bulk migration batch. Only works on jobs with. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_bulk_migration_job_password? +

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

update_bulk_migration_job_password is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_bulk_migration_job_password? +

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

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

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