complete_shared_task
Complete a shared-context task and attach the output packet if one was produced.
This record as markdown: /tools/io-github-homenshum-nodebench/complete-shared-task.md
What complete_shared_task does on Nodebench
AI agents use complete_shared_task to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why complete_shared_task is rated Medium
This tool modifies task state (marking completion) and potentially creates/attaches artifacts (output packets). These are reversible write operations. It does not execute arbitrary code (Execute), delete data (Destructive), or move funds (Financial).
From the tool's definition Tool description states 'Complete a shared-context task and attach the output packet' — the verb 'Complete' indicates state modification of a task entity, and 'attach the output packet' involves creating or modifying associated data.
Attacks that exploit this kind of access
The rule that runs complete_shared_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For complete_shared_task, this is the rule to start with:
complete_shared_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every complete_shared_task call is checked against it from then on.
Questions about complete_shared_task
Complete a shared-context task and attach the output packet if one was produced. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for complete_shared_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 Nodebench. Nothing to install.
complete_shared_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 complete_shared_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 complete_shared_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.
complete_shared_task is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue