Create and assign a task to one or more contacts. Requires a task message ID (the template for the task) and supports setting due date and assignee.
AI agents use assign_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.
This tool creates and assigns tasks to contacts, which are write operations that can be undone (tasks can be deleted, reassigned, or marked complete without permanent loss).
From the tool's definition Tool description states 'Create and assign a task', using the verb 'create' which indicates reversible data modification rather than deletion or irreversible changes.
Attacks that exploit this kind of access
Create and assign a task to one or more contacts. Requires a task message ID (the template for the task) and supports setting due date and assignee. 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 assign_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.
assign_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 assign_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 assign_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.
assign_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 →