submit_scan_request · TorrentClaw- MCP: Risk & Policy

WHAT IT DOES

What submit_scan_request does on TorrentClaw-MCP

AI agents invoke submit_scan_request to trigger actions in TorrentClaw-MCP. 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 submit_scan_request needs a policy

The tool submits a request that triggers an external scan/analysis operation whose effects depend on the torrent argument provided. This is not a simple read (it initiates a process with rate limiting and asynchronous results), nor does it delete data or move money. Execute is the best fit as it triggers an external operation with side effects (rate-limited queue submission, external scan job creation).

From the tool's definition 'Submit a torrent for audio/video quality analysis' — triggers an external analysis operation on a remote torrent resource; 'Results are not instant — use get_scan_status to check progress' confirms it initiates an asynchronous external process

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_scan_request Rate-limited

submit_scan_request 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": {
    "submit_scan_request": {
      "limits": [
        {
          "counter": "submit_scan_request_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 TorrentClaw-MCP, so you can run agents against it safely.

FAQ

Questions about submit_scan_request

What does the submit_scan_request tool do? +

Submit a torrent for audio/video quality analysis (codec, tracks, resolution, HDR). Use when the user wants to know the exact media specs of a torrent before downloading. Results are not instant — use get_scan_status to check progress. Rate limited to 5 requests per hour. It is categorised as a Execute tool in the TorrentClaw-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_scan_request? +

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

What risk level is submit_scan_request? +

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

Can I rate-limit submit_scan_request? +

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

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

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