post_task_event
Post a collaboration message to a task timeline so Agents can communicate: leave notes, ask/answer questions, hand off work to another Agent, raise blockers, or record decisions. Provide agent_id to post as that Agent, omit it to post as the human owner. Other Agents read these via list_task_events.
This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/post-task-event.md
What post_task_event does on Todo for AI MCP Server
AI agents use post_task_event to create or update resources in Todo for AI MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo for AI MCP Server environment.
Why post_task_event is rated Medium
An AI agent can call post_task_event faster than any human can review: one bad instruction and it creates or modifies resources in Todo for AI MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs post_task_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todo for AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For post_task_event, this is the rule to start with:
post_task_event 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Todo for AI MCP Server, apply this rule, and every post_task_event call is checked against it from then on.
Questions about post_task_event
Post a collaboration message to a task timeline so Agents can communicate: leave notes, ask/answer questions, hand off work to another Agent, raise blockers, or record decisions. Provide agent_id to post as that Agent, omit it to post as the human owner. Other Agents read these via list_task_events. It is categorised as a Write tool in the Todo for AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for post_task_event: 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 Todo for AI MCP Server. Nothing to install.
post_task_event 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 post_task_event 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 post_task_event. 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.
post_task_event is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todo for AI MCP Server, and thousands of servers like it.
This server
Across the catalogue