Save implementation notes, code context, or developer notes to a task. Use this to document decisions, add code snippets, or save progress notes that will help future work on this task. Context is appended (not replaced).
AI agents use add_context_to_task to create or update resources in Nubis — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nubis environment.
This tool creates or modifies data (task context) in a reversible manner. While context is appended rather than replaced, the addition of notes and code snippets to a task represents a write operation. It is not destructive because appended content can be overwritten or removed.
From the tool's definition Tool description states it 'Save[s] implementation notes, code context, or developer notes to a task' and 'Context is appended (not replaced)'. This is a write operation that modifies task data by adding content.
Attacks that exploit this kind of access
Save implementation notes, code context, or developer notes to a task. Use this to document decisions, add code snippets, or save progress notes that will help future work on this task. Context is appended (not replaced). It is categorised as a Write tool in the Nubis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nubis MCP server in PolicyLayer and add a rule for add_context_to_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 Nubis. Nothing to install.
add_context_to_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 add_context_to_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 add_context_to_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.
add_context_to_task is provided by the Nubis MCP server (@lil2good/nubis-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 →