get_scan_status

Check the status of a torrent audio/video scan request. Returns the current scan status (pending, scanning, completed, failed). Use after submit_scan_request.

Server TorrentClaw-MCP torrentclaw/torrentclaw-mcp
Category Read
Risk class Low
Parameters 00 required

What get_scan_status does on TorrentClaw-MCP

AI agents call get_scan_status to retrieve information from TorrentClaw-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_scan_status needs a policy

This tool retrieves status information about a previously submitted scan request. It is purely informational with no side effects—it queries existing data and returns a status value. This is characteristic of a Read category tool. The severity is low because status checks pose minimal risk of harm even if misused by an AI agent; the worst outcome would be information gathering about pending scans.

From the tool's definition Tool name 'get_scan_status' and description 'Check the status of a torrent audio/video scan request. Returns the current scan status (pending, scanning, completed, failed).' indicates a read-only query operation that retrieves status information without…

Questions about get_scan_status

What does the get_scan_status tool do? +

Check the status of a torrent audio/video scan request. Returns the current scan status (pending, scanning, completed, failed). Use after submit_scan_request. It is categorised as a Read tool in the TorrentClaw-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_scan_status? +

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

What risk level is get_scan_status? +

get_scan_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_scan_status? +

Yes. Add a rate_limit block to the get_scan_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.

How do I block get_scan_status completely? +

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

What MCP server provides get_scan_status? +

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

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