track_interaction · TorrentClaw- MCP: Risk & Policy

WHAT IT DOES

What track_interaction does on TorrentClaw-MCP

AI agents use track_interaction to create or update resources in TorrentClaw-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TorrentClaw-MCP environment.

WHY IT NEEDS A POLICY

Why track_interaction needs a policy

This tool writes interaction/analytics data to a backend store to update popularity statistics. It is reversible in principle (stats can be corrected), causes no code execution, and has no financial or destructive impact. The blast radius of misuse is low — at worst, popularity stats become inaccurate.

From the tool's definition Track a user interaction with a torrent (magnet link click, .torrent download, or hash copy)... to keep popularity stats accurate.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

track_interaction Rate-limited

track_interaction stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "track_interaction": {
      "limits": [
        {
          "counter": "track_interaction_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 track_interaction

What does the track_interaction tool do? +

Track a user interaction with a torrent (magnet link click, .torrent download, or hash copy). Use this after presenting a magnet link or torrent URL to the user, to keep popularity stats accurate. Fire-and-forget — does not block. It is categorised as a Write tool in the TorrentClaw-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on track_interaction? +

Register the TorrentClaw- MCP server in PolicyLayer and add a rule for track_interaction: 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 track_interaction? +

track_interaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit track_interaction? +

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

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

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