add_task_context
Add context note to task (where left off, why doing it, etc).
This record as markdown: /tools/94aharris-coach-ai/add-task-context.md
What add_task_context does on Coach AI
AI agents use add_task_context to create or update resources in Coach AI, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coach AI environment.
Why add_task_context is rated Medium
This tool creates or modifies task metadata reversibly. While it doesn't delete or execute external operations, it does alter stored task information. The severity is medium because misuse could clutter tasks with misleading context or spam notes, but the changes are easily editable or removable.
From the tool's definition add_task_context modifies task data by adding contextual notes. The tool name indicates it 'adds' content to tasks, and the description specifies it appends context notes (where left off, why doing it, etc.) to existing tasks, which is a reversible…
Attacks that exploit this kind of access
The rule that runs add_task_context safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coach AI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_task_context, this is the rule to start with:
add_task_context 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 Coach AI, apply this rule, and every add_task_context call is checked against it from then on.
Questions about add_task_context
Add context note to task (where left off, why doing it, etc). It is categorised as a Write tool in the Coach AI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coach AI MCP server in PolicyLayer and add a rule for add_task_context: 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 Coach AI. Nothing to install.
add_task_context 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 add_task_context 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 add_task_context. 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.
add_task_context is provided by the Coach AI MCP server (94aharris/coach-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coach AI, and thousands of servers like it.
This server
Across the catalogue