tm_import_capture · Tm MCP: Risk & Policy

WHAT IT DOES

What tm_import_capture does on Tm

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

WHY IT NEEDS A POLICY

Why tm_import_capture needs a policy

Without a description, confidence is reduced. The tool likely creates or modifies capture data (reversibly), placing it in Write rather than Read or Execute. Given the load-testing context (tm_analyse_capture, tm_compare_runs), an import operation could affect test datasets but is probably not irreversible or code-execution. Severity is medium due to potential to pollute test data and influence downstream analysis.

From the tool's definition Tool name 'tm_import_capture' suggests data ingestion/upload; the description is empty. Sibling tools include profile/variables set creation and deletion, indicating this server manages mutable state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tm_import_capture Rate-limited

tm_import_capture 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": {
    "tm_import_capture": {
      "limits": [
        {
          "counter": "tm_import_capture_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 Tm, so you can run agents against it safely.

FAQ

Questions about tm_import_capture

What does the tm_import_capture tool do? +

tm_import_capture. It is categorised as a Write tool in the Tm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tm_import_capture? +

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

What risk level is tm_import_capture? +

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

Can I rate-limit tm_import_capture? +

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

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

tm_import_capture is provided by the Tm MCP server (trafficmorph-gif/tm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.