[INTERNAL] Update task state. For workers only.
AI agents use update_task to create or update resources in N2n Nexus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N2n Nexus environment.
This tool creates or modifies data (task state) in a reversible manner without deleting data or executing arbitrary code. It falls under Write category. Severity is medium rather than low because task state modifications in a collaborative project management system could disrupt workflow if misused by an agent, but the impact is limited to individual task records and is reversible.
From the tool's definition Tool description states 'Update task state' which indicates modification of existing data. The [INTERNAL] tag and 'For workers only' suggest restricted access but do not prevent the categorization as a write operation since the tool modifies task state…
Documented attack patterns abuse exactly the kind of access update_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N2n Nexus, and nothing reaches the server without passing your rules. This is the rule we recommend for update_task:
{
"version": "1",
"default": "deny",
"tools": {
"update_task": {
"limits": [
{
"counter": "update_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_task 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.
Free to start. No card required.
[INTERNAL] Update task state. For workers only. It is categorised as a Write tool in the N2n Nexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the N2n Nexus MCP server in PolicyLayer and add a rule for update_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 N2n Nexus. Nothing to install.
update_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 update_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 update_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.
update_task is provided by the N2n Nexus MCP server (n2ns/n2n-nexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N2n Nexus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 N2n Nexus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.