task_complete · Outpost MCP: Risk & Policy

WHAT IT DOES

What task_complete does on Outpost

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

WHY IT NEEDS A POLICY

Why task_complete needs a policy

The tool updates task status from incomplete to complete—a modification of existing data that can generally be undone by unmarking the task. This falls under Write rather than Destructive. Severity is medium because task completion is a non-critical business function with limited blast radius; misuse would only affect the user's task list, not financial systems or irreplaceable data.

From the tool's definition Tool description states 'Mark a task as completed' which modifies task state in Microsoft To Do. This is a reversible state change (tasks can typically be uncompleted or re-opened), not an irreversible deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_complete Rate-limited

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

FAQ

Questions about task_complete

What does the task_complete tool do? +

Mark a task as completed in Microsoft To Do. It is categorised as a Write tool in the Outpost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on task_complete? +

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

What risk level is task_complete? +

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

Can I rate-limit task_complete? +

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

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

task_complete is provided by the Outpost MCP server (signalclaude/outpost). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.