Check the progress and results of a bulk email verification job. Returns status, progress percentage, summary counts, and paginated results when complete.
AI agents call verify_job_status to retrieve information from TrekMail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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.
verify_job_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →