docs(policy): include MCP DELETE in custom recipe

[HwangJohn]

Summary

Update the custom Streamable HTTP MCP network-policy recipe to include the DELETE method on the exact MCP endpoint. Some Streamable HTTP MCP clients use DELETE to terminate sessions, and the example should keep that method narrowly scoped instead of encouraging a wildcard path.

Related Issue

Refs #6329

Changes

• Document GET, POST, and DELETE for the URL-based MCP custom policy recipe.
• Add DELETE /mcp to the sample YAML while preserving the exact-path guidance.
• Extend the policy round-trip docs regression test to require the scoped DELETE rule and session-termination wording.

Type of Change

• Code change (feature, bug fix, or refactor)
• Code change with doc updates
• Doc only (prose changes, no code sample modifications)
• Doc only (includes code sample changes)

Quality Gates

• Tests added or updated for changed behavior
• Existing tests cover changed behavior — justification:
• Tests not applicable — justification:
• Docs updated for user-facing behavior changes
• Docs not applicable — justification:
• Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
• Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: self-review confirmed this is a doc/test-only policy recipe update that adds DELETE only for the exact /mcp endpoint and preserves the warning against /** wildcard paths.
• Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Verification

• PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
• Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run check:diff passed when hooks were skipped or unavailable — npm run check:diff passed on DGX Spark/Linux.
• Targeted behavior tests pass for the current change set, or tests are marked not applicable above — npx vitest run --project integration test/policy-roundtrip-docs.test.ts passed on DGX Spark/Linux (3 tests).
• Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result:
• Quality Gates section completed with required justifications or waivers
• No secrets, API keys, or credentials committed
• npm run docs builds without warnings (doc changes only) — npm run docs passed on DGX Spark/Linux with 0 errors; Fern reported only the existing upgrade warning.
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

---

Signed-off-by: HwangJohn angelic805@gmail.com

Summary by CodeRabbit

• Documentation

  • Updated the URL-Based MCP Server network policy example to allow DELETE requests on the /mcp endpoint.
  • Clarified that the endpoint supports GET, POST, and DELETE, including session termination.

• Tests

  • Added coverage to verify the updated policy example and session-termination guidance.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 1af63a6f-c19e-421d-8649-0897af55eaa6

📥 Commits

Reviewing files that changed from the base of the PR and between 14dc22c and 5b37a67.

📒 Files selected for processing (2)

• docs/network-policy/customize-network-policy.mdx
• test/policy-roundtrip-docs.test.ts

---

📝 Walkthrough

Walkthrough

The URL-Based MCP network-policy recipe now permits DELETE on /mcp, updates its method guidance, and verifies the rule and session-termination text in documentation tests.

Changes

MCP policy documentation

Layer / File(s)	Summary
Document and validate DELETE access docs/network-policy/customize-network-policy.mdx, test/policy-roundtrip-docs.test.ts	The recipe documents GET, POST, and DELETE for /mcp, adds the corresponding YAML allow rule, and extends round-trip assertions for the rule and session-termination guidance.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: documenting MCP DELETE support in the custom recipe.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[prekshivyas]

PR Review Advisor — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: Add or justify PRA-T1 and any related test follow-ups.
Open items: 0 required · 0 warnings · 0 suggestions · 5 test follow-ups
Since last review: 0 prior items resolved · 0 still apply · 0 new items found

Action checklist

• PRA-T1 Add or justify test follow-up: Acceptance clause
• PRA-T2 Add or justify test follow-up: Acceptance clause
• PRA-T3 Add or justify test follow-up: Acceptance clause
• PRA-T4 Add or justify test follow-up: Acceptance clause
• PRA-T5 Add or justify test follow-up: Acceptance clause

Test follow-ups to resolve or justify

If these cover changed behavior, prefer adding them in this PR; otherwise state why existing coverage is enough or link the follow-up.

• PRA-T1 Acceptance clause — We are using openshell nemoclaw version .71 and inside hemes agent sandbox version .17. While on lower version this issue was never faced, on the current version we observed that some of the network policies get automatically rejected during the agent turns although they are approved previously. — add test evidence or identify existing coverage. This PR does not change runtime OpenShell/NemoClaw policy state-transition code; it changes only `docs/network-policy/customize-network-policy.mdx` and `test/policy-roundtrip-docs.test.ts`. The linked issue comment attributes the approved-to-rejected state flip to an OpenShell gateway governance-ledger behavior rather than this documentation recipe.
• PRA-T2 Acceptance clause — 2026-07-06T13:16:38.626Z OCSF HTTP:DELETE [MED] DENIED /usr/bin/python3.13(392063) -> DELETE http://172.17.0.1:8090/v1/mcp [policy:spiceai engine:l7] [reason:FORWARD_L7 deny DELETE 172.17.0.1:8090/v1/mcp reason=DELETE /v1/mcp not permitted by policy] — add test evidence or identify existing coverage. The diff documents the analogous Streamable HTTP MCP method requirement by adding `- allow: { method: DELETE, path: "/mcp" }` to the custom URL-based MCP recipe. It does not change a built-in SpiceAI preset or the reported `/v1/mcp` runtime policy.
• PRA-T3 Acceptance clause — Suggest tracking "MCP policy presets should permit DELETE on the MCP path" as its own NemoClaw issue; it is independent of the self-reject bug. — add test evidence or identify existing coverage. The PR addresses the custom documentation recipe for URL-based MCP policy additions, not checked-in built-in policy presets. A read-only search under `nemoclaw-blueprint` found no `*spice*` preset file in this narrow review scope.
• PRA-T4 Acceptance clause — 1. Deploy nemoclaw with hermes as mentioned versions. — add test evidence or identify existing coverage. No deployment, Hermes runtime, sandbox lifecycle, or versioned execution path changed in this PR.
• PRA-T5 Acceptance clause — 2. Keep restrictiveness to medium. Choose all other parameters as default during deployment. — add test evidence or identify existing coverage. No onboarding restrictiveness, policy tier, or default deployment code changed in this PR.

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

[prekshivyas]

PR Review Advisor (Nemotron Ultra) — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: No advisor follow-up required beyond maintainer review.
Open items: 0 required · 0 warnings · 0 suggestions · 0 test follow-ups
Since last review: 0 prior items resolved · 0 still apply · 0 new items found

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

[prekshivyas]

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: target/main
Head: HEAD
Confidence: high

Required E2E

• None. No E2E is recommended. The PR is limited to documentation and a docs-focused unit test asserting the documented policy example text. It does not change runtime code, YAML policy assets used by NemoClaw, onboarding/resume state, sandbox lifecycle, credentials, security enforcement, inference routing, deployment, or real assistant user flows. The deterministic risk plan also lists no required jobs.

Optional E2E

• None.

New E2E recommendations

• None.

[cv]

Approved on exact head 5b37a67. All five required checks pass; DCO/signatures are verified; CodeRabbit has no threads; trusted advisor run 29135641592 has both exact-head models at merge_as_is with zero findings and unit coverage sufficient. No live E2E target is required. The remaining canceled commit-lint/DCO contexts are superseded duplicates, and the advisor gate miss is absent run_attempt metadata rather than absent analysis.