createMission
Create a new mission with title, type, success criteria, output contract, and budget.
This record as markdown: /tools/io-github-homenshum-nodebench/createmission.md
What createMission does on Nodebench
AI agents use createMission 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 createMission is rated Medium
This tool creates and stores new mission records. It is reversible (missions can typically be deleted or modified), so it falls under Write rather than Destructive. The blast radius is medium because a misconfigured or malicious mission could commit resources (budget) or establish incorrect success criteria, but it does not directly execute code, delete data irreversibly, or transfer financial funds.
From the tool's definition Tool creates a new mission with title, type, success criteria, output contract, and budget. The word 'create' and the action of establishing a new record with multiple parameters (title, type, success criteria, output contract, budget) indicates data creation.
Attacks that exploit this kind of access
The rule that runs createMission 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 createMission, this is the rule to start with:
createMission 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 createMission call is checked against it from then on.
Questions about createMission
Create a new mission with title, type, success criteria, output contract, and budget. 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 createMission: 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.
createMission 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 createMission 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 createMission. 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.
createMission 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