submit_delx_mission

Submit independently checkable evidence for an accepted DELX mission. Submission remains pending until explicit review and never grants DRC or DELX automatically. Free

SERVERDelx Protocol — Agent Recovery & Continuity SOURCEhttps://api.delx.ai/v1/mcp?src=registry

Medium RISK CLASS

Category Write

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-protocol/submit-delx-mission.md

WHAT IT DOES

What submit_delx_mission does on Delx Protocol — Agent Recovery & Continuity

AI agents use submit_delx_mission to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.

Parameter	Type	Required	Description
`output`	object	—	Structured findings/outcome report
`agent_id`	string	Yes	Stable Delx agent identifier
`mission_id`	string	Yes	Active mission id returned by get_delx_missions
`target_url`	string	—	Optional audited target URL
`agent_token`	string	Yes	Agent token returned by /api/v1/agents/register
`evidence_uri`	string	—	Public sanitized evidence URL
`artifact_hash`	string	—	Immutable sha256 evidence hash
`controller_id`	string	—	Optional fleet/controller identifier

Parameters from the server's own tool schema.

RISK

Why submit_delx_mission is rated Medium

An AI agent can call submit_delx_mission faster than any human can review: one bad instruction and it creates or modifies resources in Delx Protocol — Agent Recovery & Continuity by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs submit_delx_mission safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_delx_mission, this is the rule to start with:

submit_delx_mission Rate-limited

submit_delx_mission 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_delx_mission": {
      "limits": [
        {
          "counter": "submit_delx_mission_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every submit_delx_mission call is checked against it from then on.

FAQ

Questions about submit_delx_mission

What does the submit_delx_mission tool do? +

Submit independently checkable evidence for an accepted DELX mission. Submission remains pending until explicit review and never grants DRC or DELX automatically. Free. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does submit_delx_mission accept? +

submit_delx_mission accepts 8 parameters: output, agent_id, mission_id, target_url, agent_token, evidence_uri, artifact_hash, controller_id. Required: agent_id, mission_id, agent_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on submit_delx_mission? +

Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for submit_delx_mission: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.

What risk level is submit_delx_mission? +

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

Can I rate-limit submit_delx_mission? +

Yes. Add a rate_limit block to the submit_delx_mission 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_delx_mission completely? +

Set action: deny in the PolicyLayer policy for submit_delx_mission. 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_delx_mission? +

submit_delx_mission is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.

This server

All 1076 Delx Protocol — Agent Recovery & Continuity tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →