cvat_attach_task_data · CVAT MCP: Risk & Policy

WHAT IT DOES

What cvat_attach_task_data does on CVAT MCP

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

WHY IT NEEDS A POLICY

Why cvat_attach_task_data needs a policy

This tool creates or modifies data reversibly by attaching media files to annotation tasks. The POST method with upload headers confirms it writes data to the server. It is not destructive (no deletion), not financial, and not arbitrary code execution — it is scoped to media attachment within CVAT.

From the tool's definition Tool description explicitly states 'Attach local, server, or remote media to a task using POST /api/tasks/{id}/data/' — POST is a write operation that modifies task state by adding media attachments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cvat_attach_task_data Rate-limited

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

FAQ

Questions about cvat_attach_task_data

What does the cvat_attach_task_data tool do? +

Attach local, server, or remote media to a task using POST /api/tasks/{id}/data/ with CVAT upload headers. It is categorised as a Write tool in the CVAT 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 cvat_attach_task_data? +

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

What risk level is cvat_attach_task_data? +

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

Can I rate-limit cvat_attach_task_data? +

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

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

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