New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

verify_cancel_job

Cancel a running verification job. Unprocessed credits are automatically refunded.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/verify-cancel-job.md

What verify_cancel_job does on TrekMail MCP Server

AI agents call verify_cancel_job to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why verify_cancel_job is rated Critical

Cancelling a running verification job is an irreversible action that terminates an in-progress process. While credits are refunded, the job itself cannot be resumed once cancelled — it must be restarted from scratch. The financial credit refund aspect is incidental and automatic, not the primary action. The primary action is irreversible termination of a running job, placing this in Destructive.

From the tool's definition Cancel a running verification job. Unprocessed credits are automatically refunded.

Questions about verify_cancel_job

What does the verify_cancel_job tool do? +

Cancel a running verification job. Unprocessed credits are automatically refunded. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on verify_cancel_job? +

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

verify_cancel_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit verify_cancel_job? +

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

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

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

More on TrekMail MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TrekMail MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.