verify_job_status

Check the progress and results of a bulk email verification job. Returns status, progress percentage, summary counts, and paginated results when complete.

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/verify-job-status.md

WHAT IT DOES

What verify_job_status does on TrekMail MCP Server

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

This tool queries and retrieves information about an existing bulk email verification job's progress and results. It performs no modifications, deletions, or external operations—only reading status data. This is a classic Read operation with minimal risk, as it cannot alter system state or trigger unintended actions.

From the tool's definition Tool name 'verify_job_status' and description 'Check the progress and results' indicate retrieval of job status data. Words like 'returns status, progress percentage, summary counts' confirm this is a data retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

verify_job_status Allowed

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

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

FAQ

Questions about verify_job_status

What does the verify_job_status tool do? +

Check the progress and results of a bulk email verification job. Returns status, progress percentage, summary counts, and paginated results when complete. 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 verify_job_status? +

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

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

Can I rate-limit verify_job_status? +

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

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

verify_job_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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