accept_shared_task

Accept a proposed shared-context task.

SERVERNodebench SOURCEnodebench-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/accept-shared-task.md

WHAT IT DOES

What accept_shared_task does on Nodebench

AI agents use accept_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.

RISK

Why accept_shared_task is rated Medium

Accepting a task modifies shared state by committing to or activating a proposed task, which is a reversible write operation. It doesn't delete data or execute code, but it does change the state of a task from proposed to accepted, affecting shared context.

From the tool's definition Accept a proposed shared-context task

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs accept_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 accept_shared_task, this is the rule to start with:

accept_shared_task Rate-limited

accept_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "accept_shared_task": {
      "limits": [
        {
          "counter": "accept_shared_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every accept_shared_task call is checked against it from then on.

FAQ

Questions about accept_shared_task

What does the accept_shared_task tool do? +

Accept a proposed shared-context task. 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.

How do I enforce a policy on accept_shared_task? +

Register the Nodebench MCP server in PolicyLayer and add a rule for accept_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.

What risk level is accept_shared_task? +

accept_shared_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit accept_shared_task? +

Yes. Add a rate_limit block to the accept_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.

How do I block accept_shared_task completely? +

Set action: deny in the PolicyLayer policy for accept_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.

What MCP server provides accept_shared_task? +

accept_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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →