# submit_fix_outcome

Report back whether a Denpex fix actually resolved the failure. Call this after you apply a fix from diagnose_crash and observe the result — it is the ONLY way the engine learns, and it directly improves the next diagnosis of this failure class for you and everyone else. Pass the diagnosisId printed at the bottom of the diagnosis. If the fix did not work, say what actually happened in note (and newFix if you found the real one) — a specific negative is worth more than a vague positive.

Agent View of the PolicyLayer registry record for `submit_fix_outcome`. HTML page: https://policylayer.com/tools/denpex-mcp/submit-fix-outcome

## Facts

- Tool: `submit_fix_outcome`
- Server: Denpex (`denpex-mcp`) — https://policylayer.com/tools/denpex-mcp.md
- Install: `npx -y denpex-mcp`
- Homepage: https://www.npmjs.com/package/denpex-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 4 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `note` | string | no | What actually happened. On a `did_not_work`, this is the most valuable field in the call — say what the log showed after the fix. |
| `newFix` | string | no | If you found the real fix, what was it? |
| `outcome` | string | yes | `worked` = the failure is resolved and the job is progressing. `did_not_work` = it recurred or the fix did not apply. |
| `diagnosisId` | string | yes | The `diagnosisId` from the diagnosis you acted on. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "submit_fix_outcome",
    "arguments": {
      "outcome": "<outcome>",
      "diagnosisId": "<diagnosisId>"
    }
  }
}
```

## Why submit_fix_outcome is rated Medium

An AI agent can call submit_fix_outcome faster than any human can review: one bad instruction and it creates or modifies resources in Denpex by the hundred, each call as confident as the last.

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Denpex:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_fix_outcome": {
      "limits": [
        {
          "counter": "submit_fix_outcome_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Denpex (14)

- `compare_runs` — Execute — https://policylayer.com/tools/denpex-mcp/compare-runs.md
- `diff_environments` — Execute — https://policylayer.com/tools/denpex-mcp/diff-environments.md
- `node_health` — Execute — https://policylayer.com/tools/denpex-mcp/node-health.md
- `predict_failures` — Execute — https://policylayer.com/tools/denpex-mcp/predict-failures.md
- `analyze_cascade` — Read — https://policylayer.com/tools/denpex-mcp/analyze-cascade.md
- `ask_followup` — Read — https://policylayer.com/tools/denpex-mcp/ask-followup.md
- `check_quota` — Read — https://policylayer.com/tools/denpex-mcp/check-quota.md
- `check_versions` — Read — https://policylayer.com/tools/denpex-mcp/check-versions.md
- `diagnose_crash` — Read — https://policylayer.com/tools/denpex-mcp/diagnose-crash.md
- `list_incidents` — Read — https://policylayer.com/tools/denpex-mcp/list-incidents.md
- `lookup_failure` — Read — https://policylayer.com/tools/denpex-mcp/lookup-failure.md
- `preflight_check` — Read — https://policylayer.com/tools/denpex-mcp/preflight-check.md
- `recent_diagnoses` — Read — https://policylayer.com/tools/denpex-mcp/recent-diagnoses.md
- `validate_checkpoint` — Read — https://policylayer.com/tools/denpex-mcp/validate-checkpoint.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=denpex-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/denpex-mcp