submit_my_output · Dag Planner MCP: Risk & Policy

WHAT IT DOES

What submit_my_output does on Dag Planner

AI agents use submit_my_output to create or update resources in Dag Planner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dag Planner environment.

WHY IT NEEDS A POLICY

Why submit_my_output needs a policy

The tool creates or modifies persistent state (task completion status and output data) within the DAG planner system. While reversible via other tools or replay, submitting task output is a write that affects downstream task dependencies and workflow execution. Not Destructive (not irreversible deletion), not Execute (it does not run arbitrary code), not Financial.

From the tool's definition Tool description states 'Submit final output and mark task completed' — this modifies task state durably by recording completion and output, making it a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_my_output Rate-limited

submit_my_output 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_my_output": {
      "limits": [
        {
          "counter": "submit_my_output_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dag Planner, so you can run agents against it safely.

FAQ

Questions about submit_my_output

What does the submit_my_output tool do? +

Submit final output and mark task completed. It is categorised as a Write tool in the Dag Planner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_my_output? +

Register the Dag Planner MCP server in PolicyLayer and add a rule for submit_my_output: 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 Dag Planner. Nothing to install.

What risk level is submit_my_output? +

submit_my_output is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_my_output? +

Yes. Add a rate_limit block to the submit_my_output 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.

How do I block submit_my_output completely? +

Set action: deny in the PolicyLayer policy for submit_my_output. 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.

What MCP server provides submit_my_output? +

submit_my_output is provided by the Dag Planner MCP server (shubhamnegi/dag-planner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.