reject_shared_task
Reject a proposed shared-context task with a reason.
This record as markdown: /tools/io-github-homenshum-nodebench/reject-shared-task.md
What reject_shared_task does on Nodebench
AI agents use reject_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 reject_shared_task is rated Medium
This tool performs a reversible state modification (rejection can potentially be undone or overridden by accepting the task later, or by administrative action). It does not execute code, delete data irreversibly, or access financial systems.
From the tool's definition Tool description states it will 'Reject a proposed shared-context task with a reason' — this modifies the state of a task by changing its status from proposed/pending to rejected, and records a reason.
Attacks that exploit this kind of access
The rule that runs reject_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 reject_shared_task, this is the rule to start with:
reject_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 reject_shared_task call is checked against it from then on.
Questions about reject_shared_task
Reject a proposed shared-context task with a reason. 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 reject_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.
reject_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 reject_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 reject_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.
reject_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