migrate_task_run_logs · Qontinui MCP Server MCP

WHAT IT DOES

What migrate_task_run_logs does on Qontinui MCP Server

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

WHY IT NEEDS A POLICY

Why migrate_task_run_logs needs a policy

The tool writes log data to a persistent database (SQLite), which is a reversible modification operation. While it affects stored state, the data being migrated is log information rather than core business data. The severity is medium because misuse could lead to database bloat, storage issues, or overwriting of legitimate logs, but the impact is limited to logging infrastructure.

From the tool's definition Tool description states: 'Migrate JSONL logs to SQLite for a task run. This persists the current .dev-logs/*.jsonl files to the database linked to the task run.' The verb 'persists' and the action of moving/storing logs into a database indicates data…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_task_run_logs Rate-limited

migrate_task_run_logs 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": {
    "migrate_task_run_logs": {
      "limits": [
        {
          "counter": "migrate_task_run_logs_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 Qontinui MCP Server, so you can run agents against it safely.

FAQ

Questions about migrate_task_run_logs

What does the migrate_task_run_logs tool do? +

Migrate JSONL logs to SQLite for a task run. This persists the current .dev-logs/*.jsonl files to the database linked to the task run. Call this after task completion to preserve logs. It is categorised as a Write tool in the Qontinui MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on migrate_task_run_logs? +

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

What risk level is migrate_task_run_logs? +

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

Can I rate-limit migrate_task_run_logs? +

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

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

migrate_task_run_logs is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.