mark_task_done · Amazing Marvin MCP: Risk & Policy

WHAT IT DOES

What mark_task_done does on Amazing Marvin MCP

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

WHY IT NEEDS A POLICY

Why mark_task_done needs a policy

This tool creates a reversible state change to a task's completion status. It is a Write operation because it modifies data (task state) without permanent deletion. Severity is medium because misuse could result in incorrect task completion records affecting user productivity workflows, but the action is reversible (task can be unmarked/reopened).

From the tool's definition Tool description states 'Mark a task as completed in Amazing Marvin.' This modifies task state by changing completion status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_task_done Rate-limited

mark_task_done 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": {
    "mark_task_done": {
      "limits": [
        {
          "counter": "mark_task_done_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 Amazing Marvin MCP, so you can run agents against it safely.

FAQ

Questions about mark_task_done

What does the mark_task_done tool do? +

Mark a task as completed in Amazing Marvin. It is categorised as a Write tool in the Amazing Marvin 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 mark_task_done? +

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

What risk level is mark_task_done? +

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

Can I rate-limit mark_task_done? +

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

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

mark_task_done is provided by the Amazing Marvin MCP server (qemqemqem/amazing-marvin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.