check_transmission

Check Transmission BitTorrent client RPC health via GET /transmission/rpc. A 409 response (CSRF token required) confirms Transmission is running. Default port 9091.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-transmission.md

WHAT IT DOES

What check_transmission does on Mcp Nettools

AI agents call check_transmission to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_transmission is rated Low

This tool queries the status of a local service (Transmission BitTorrent client) through a GET HTTP request. It has no side effects—it only reads the health status and does not create, modify, delete, or execute arbitrary code. The CSRF token requirement is a security feature, not an indication of destructive capability.

From the tool's definition Tool performs a health check via GET request to /transmission/rpc endpoint, checking if Transmission BitTorrent client is running. GET request with CSRF token validation is a read-only operation that retrieves service status without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_transmission safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_transmission, this is the rule to start with:

check_transmission Allowed

check_transmission is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_transmission": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_transmission call is checked against it from then on.

FAQ

Questions about check_transmission

What does the check_transmission tool do? +

Check Transmission BitTorrent client RPC health via GET /transmission/rpc. A 409 response (CSRF token required) confirms Transmission is running. Default port 9091. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_transmission? +

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

What risk level is check_transmission? +

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

Can I rate-limit check_transmission? +

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

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

check_transmission is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →