create-task · Back-Agent MCP Server MCP: Risk & Policy

WHAT IT DOES

What create-task does on Back-Agent MCP Server

AI agents invoke create-task to trigger actions in Back-Agent MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why create-task needs a policy

Creating a task for an AI programming assistant that executes code generation and development tasks in working directories constitutes an Execute-level action. While named 'create-task' (suggesting Write), the server's core purpose is to trigger automated code generation and task completion via Claude Code CLI, making the effective action Execute.

From the tool's definition 'creates a background task for an AI programming assistant' that bridges 'Claude Desktop with Claude Code CLI, enabling automated code generation and task completion'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-task Rate-limited

create-task stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-task": {
      "limits": [
        {
          "counter": "create-task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Back-Agent MCP Server, so you can run agents against it safely.

FAQ

Questions about create-task

What does the create-task tool do? +

IMPORTANT: This creates a background task for an AI programming assistant, NOT a direct shell command executor.\n\n. It is categorised as a Execute tool in the Back-Agent MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create-task? +

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

What risk level is create-task? +

create-task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create-task? +

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

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

create-task is provided by the Back-Agent MCP Server MCP server (zuens2020/back-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.