submit_durable_tasks
Submit a worker batch behind an internal durable task handle.
This record as markdown: /tools/mcp-control-plane/submit-durable-tasks.md
What submit_durable_tasks does on Mcp Control Plane
AI agents invoke submit_durable_tasks to trigger actions in Mcp Control Plane. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why submit_durable_tasks is rated High
Submitting a worker batch triggers execution of tasks on the server. The durable nature means these tasks run persistently and may have broad side effects depending on what the workers do. This falls under Execute as it triggers external operations whose effects depend on arguments.
From the tool's definition 'Submit a worker batch behind an internal durable task handle' — submits batch tasks to durable workers for execution
Attacks that exploit this kind of access
The rule that runs submit_durable_tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_durable_tasks, this is the rule to start with:
submit_durable_tasks stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every submit_durable_tasks call is checked against it from then on.
Questions about submit_durable_tasks
Submit a worker batch behind an internal durable task handle. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for submit_durable_tasks: 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 Mcp Control Plane. Nothing to install.
submit_durable_tasks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the submit_durable_tasks 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 submit_durable_tasks. 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.
submit_durable_tasks is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue