accept_delx_mission
Accept one active DELX mission for an authenticated agent. Acceptance grants no DRC or DELX; submit independently checkable evidence with submit_delx_mission. Free
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/accept-delx-mission.md
What accept_delx_mission does on Delx Mcp A2a
AI agents call accept_delx_mission to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | Stable Delx agent identifier |
mission_id | string | Yes | Active mission id returned by get_delx_missions |
agent_token | string | Yes | Agent token returned by /api/v1/agents/register |
controller_id | string | — | Optional fleet/controller identifier |
Parameters from the server's own tool schema.
Why accept_delx_mission is rated Low
Even though accept_delx_mission only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs accept_delx_mission safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For accept_delx_mission, this is the rule to start with:
accept_delx_mission 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 Delx Mcp A2a, apply this rule, and every accept_delx_mission call is checked against it from then on.
Questions about accept_delx_mission
Accept one active DELX mission for an authenticated agent. Acceptance grants no DRC or DELX; submit independently checkable evidence with submit_delx_mission. Free. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
accept_delx_mission accepts 4 parameters: agent_id, mission_id, agent_token, controller_id. Required: agent_id, mission_id, agent_token. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for accept_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 Mcp A2a. Nothing to install.
accept_delx_mission 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 accept_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.
Set action: deny in the PolicyLayer policy for accept_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.
accept_delx_mission is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue