Bug Description
The unbound_manage tool's settingsDelHostOverride method returns {"result":"not found"} even when the UUID exists and is valid.
Root Cause
The MCP server appears to pass the UUID as a JSON body parameter instead of in the URL path. The OPNsense API expects:
POST /api/unbound/settings/delHostOverride/{uuid}
But the MCP server seems to be calling:
POST /api/unbound/settings/delHostOverride
Body: { "uuid": "..." }
Steps to Reproduce
- Create a host override using
settingsAddHostOverride
- Verify it exists via
settingsGet (UUID visible in response)
- Try to delete using
settingsDelHostOverride with params: { uuid: "..." }
- Returns
{"result":"not found"}
Workaround
Direct curl call with UUID in path works:
curl -k -X POST "https://opnsense/api/unbound/settings/delHostOverride/{uuid}"
Environment
- opnsense-mcp-server: v0.6.0
- OPNsense: 25.x
Affected Methods
Likely affects all settingsDel* methods that require UUID in URL path.
Bug Description
The
unbound_managetool'ssettingsDelHostOverridemethod returns{"result":"not found"}even when the UUID exists and is valid.Root Cause
The MCP server appears to pass the UUID as a JSON body parameter instead of in the URL path. The OPNsense API expects:
POST /api/unbound/settings/delHostOverride/{uuid}
But the MCP server seems to be calling:
POST /api/unbound/settings/delHostOverride
Body: { "uuid": "..." }
Steps to Reproduce
settingsAddHostOverridesettingsGet(UUID visible in response)settingsDelHostOverridewithparams: { uuid: "..." }{"result":"not found"}Workaround
Direct curl call with UUID in path works: