start_deep_scan · Intodns MCP: Risk & Policy

WHAT IT DOES

What start_deep_scan does on Intodns

AI agents invoke start_deep_scan to trigger actions in Intodns. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_deep_scan needs a policy

This tool executes an external scanning operation on remote DNS/email infrastructure. While not destructive or financial, it performs a substantive action (triggering a third-party scanning service) that could be misused to scan unauthorized systems or consume resources.

From the tool's definition Tool initiates a 'long-running Internet.nl deep scan', which triggers an external operation (network scanning) whose effects depend on the target argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_deep_scan Rate-limited

start_deep_scan stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_deep_scan": {
      "limits": [
        {
          "counter": "start_deep_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about start_deep_scan

What does the start_deep_scan tool do? +

Start a long-running Internet.nl deep scan (typically 30-120s). Returns a. It is categorised as a Execute tool in the Intodns MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_deep_scan? +

Register the Intodns MCP server in PolicyLayer and add a rule for start_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 start_deep_scan? +

start_deep_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_deep_scan? +

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

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

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