delegate_founder_issue
Create a bounded shared task handoff for a founder issue packet so the weak angle becomes assigned work.
This record as markdown: /tools/io-github-homenshum-nodebench/delegate-founder-issue.md
What delegate_founder_issue does on Nodebench
AI agents use delegate_founder_issue 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 delegate_founder_issue is rated Medium
The tool creates or modifies task/assignment data by generating a new shared task handoff. This is a Write operation (creates/assigns work) rather than Read (it generates new state), Execute (no code execution), or Destructive (reversible). Severity is medium because misuse could create incorrect task assignments or workload imbalances, but the effect is reversible (tasks can be reassigned).
From the tool's definition Tool creates a 'bounded shared task handoff' for a 'founder issue packet', indicating it writes/creates a new task assignment or delegation record.
Attacks that exploit this kind of access
The rule that runs delegate_founder_issue 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 delegate_founder_issue, this is the rule to start with:
delegate_founder_issue 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 delegate_founder_issue call is checked against it from then on.
Questions about delegate_founder_issue
Create a bounded shared task handoff for a founder issue packet so the weak angle becomes assigned work. 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 delegate_founder_issue: 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.
delegate_founder_issue 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 delegate_founder_issue 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 delegate_founder_issue. 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.
delegate_founder_issue 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