cancel_deep_scan

Cancel an in-progress Internet.nl deep scan. Idempotent DELETE — safe to call even if scan already finished or never started (returns acknowledgement either way). Requires

Server Intodns rosconl/intodns-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What cancel_deep_scan does on Intodns

AI agents call cancel_deep_scan to permanently remove resources in Intodns — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why cancel_deep_scan needs a policy

The tool issues a DELETE operation to cancel a running scan. While it is idempotent and described as safe, it irreversibly terminates an in-progress scan process that cannot be resumed. This qualifies as Destructive since the cancellation cannot be undone (a cancelled scan must be restarted from scratch).

From the tool's definition Cancel an in-progress Internet.nl deep scan. Idempotent DELETE — safe to call even if scan already finished or never started

Questions about cancel_deep_scan

What does the cancel_deep_scan tool do? +

Cancel an in-progress Internet.nl deep scan. Idempotent DELETE — safe to call even if scan already finished or never started (returns acknowledgement either way). Requires. It is categorised as a Destructive tool in the Intodns 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 cancel_deep_scan? +

Register the Intodns MCP server in PolicyLayer and add a rule for cancel_deep_scan: 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 Intodns. Nothing to install.

What risk level is cancel_deep_scan? +

cancel_deep_scan 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 cancel_deep_scan? +

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

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

cancel_deep_scan is provided by the Intodns MCP server (rosconl/intodns-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.