Mark a task as complete. Provide either a taskId (from getTasks) or searchText to fuzzy-match the task.
AI agents use markTaskDone to create or update resources in Knowledge MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Knowledge MCP Server environment.
This tool modifies existing data (task status) but the operation is reversible; a task marked done can be undone or rescheduled. It does not delete data irreversibly, execute arbitrary code, or move money.
From the tool's definition markTaskDone marks a task as complete, which modifies the state of a task from incomplete to done. This is a reversible state change—the task can be unmarked or reopened.
Attacks that exploit this kind of access
Mark a task as complete. Provide either a taskId (from getTasks) or searchText to fuzzy-match the task. It is categorised as a Write tool in the Knowledge MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Knowledge MCP Server MCP server in PolicyLayer and add a rule for markTaskDone: 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 Knowledge MCP Server. Nothing to install.
markTaskDone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the markTaskDone 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.
Set action: deny in the PolicyLayer policy for markTaskDone. 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.
markTaskDone is provided by the Knowledge MCP Server MCP server (vuluu2k/knowledge_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →