joesproxy_diagnose

prompt · Connected client

Before you start

Start with the symptom you observed in the app. Fetch the diagnostic playbook first; any capture reads or proposed changes it suggests need their own permissions.

Use an enrolled MCP client and check prompts/list for this name. Reading the prompt does not run its steps.

Request

{
  "method": "prompts/get",
  "params": {
    "name": "joesproxy_diagnose"
  }
}

Illustrative usage; your identifiers and available evidence will differ.

What to look for

Get the diagnostic playbook. Treat its suggested investigations as guidance, not automatic approval.

If the result is unexpected

List prompts available to this client. Fetching a prompt does not run the investigation or authorize changes.

Effects and cleanup

This request reads information; it does not start a test or activate a traffic change. Treat returned metadata and any exported evidence as potentially sensitive.

Browse all MCP reference entries →