getTasksForMission
Get all task plans for a mission, showing execution status, dependencies, and assigned agents.
This record as markdown: /tools/io-github-homenshum-nodebench/gettasksformission.md
What getTasksForMission does on Nodebench
AI agents call getTasksForMission to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getTasksForMission is rated Low
This tool retrieves or lists data (task plans, their status, dependencies, and agent assignments) with no side effects. It fits the Read category as a straightforward query/get operation. Severity is low because reading task information poses minimal risk; an AI agent accessing this data cannot cause financial loss, delete resources, or execute arbitrary code.
From the tool's definition Tool name 'getTasksForMission' and description 'Get all task plans for a mission, showing execution status, dependencies, and assigned agents' indicate a retrieval operation that queries and returns information about existing tasks without modifying,…
Attacks that exploit this kind of access
The rule that runs getTasksForMission 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 getTasksForMission, this is the rule to start with:
getTasksForMission is read-only, so it stays allowed. 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 getTasksForMission call is checked against it from then on.
Questions about getTasksForMission
Get all task plans for a mission, showing execution status, dependencies, and assigned agents. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for getTasksForMission: 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.
getTasksForMission is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getTasksForMission 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 getTasksForMission. 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.
getTasksForMission 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