Mark one or more tasks as completed. Optionally include a task outcome and followup task data.
AI agents use complete_task to create or update resources in Ontraport MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ontraport MCP Server environment.
Completing a task is a state change to existing data that could be undone (task could be reopened), placing it in the Write category rather than Execute. While this impacts workflow operations, it does not trigger external code execution, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Mark one or more tasks as completed.' This modifies the state of existing tasks (completion status), making it a reversible write operation.
Attacks that exploit this kind of access
Mark one or more tasks as completed. Optionally include a task outcome and followup task data. It is categorised as a Write tool in the Ontraport MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ontraport MCP Server MCP server in PolicyLayer and add a rule for complete_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 Ontraport MCP Server. Nothing to install.
complete_task 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 complete_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.
Set action: deny in the PolicyLayer policy for complete_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.
complete_task is provided by the Ontraport MCP Server MCP server (landonray/mcp-server). 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 →