[Automated] Draft docs (agentgateway): mcp: expose list/* results into CEL

[github-actions]

Documentation triage

1 candidates, 1 triaged, 0 skipped.

Product	scoped-edit
agentgateway	1

Feature clusters

Kept apart on purpose. Merging wrongly produces a guide that documents two things and explains neither, so these are reported for a person to merge rather than grouped automatically:

• mcp: expose list/* results into CEL agentgateway#3601, Parse MCP context for CEL early agentgateway#3301 all mention "CEL" in the title and are in different clusters; check whether they are one feature

Draft a documentation change

agentgateway/agentgateway#3601 — mcp: expose list/* results into CEL

• Product: agentgateway (upstream) → agentgateway/website
• Docs version: standalone/main, kubernetes/main
• Summary (read from the body): Similar to how we do it for tool call
• Not tested: no cluster was available, so every command in this diff is unrun — cluster probing disabled for this run
• No rule covers 1 touched file(s). The candidate pages below come from the files that DID match a rule, so they may scope this narrower than the change is. Read these before deciding the change is only about the pages listed:
  • schema/cel.md

How this page was chosen

• Disposition: pr
• Why:
  • this change adds, removes and rewords no configuration field, so the identifier search had nothing to look for. Read it as a behavior change to a page the code-path rules name, not as new surface, and edit the page that already describes that behavior
  • 33 editable candidate page(s), none of them named by a rule: they are in scope by location alone, so treat the chosen page as the weakest claim in this pull request. The candidates span 2 separate documentation trees (kubernetes, standalone), which do not share prose, so cover each tree that has a candidate rather than choosing between them, and say which pages you covered
  • no release-note block in this repository's template; the summary above was read from the pull request body, not written by the author
• Candidate pages:
  • assets/agw-docs/pages/reference/cel/custom-functions.md (editable here)
  • content/docs/standalone/main/documentation/mcp/_index.md (editable here)
  • content/docs/standalone/main/documentation/mcp/about.md (editable here)
  • content/docs/standalone/main/documentation/mcp/apps.md (editable here)
  • content/docs/standalone/main/documentation/mcp/configuration-modes.md (editable here)
  • content/docs/standalone/main/documentation/mcp/connect.md (editable here)
  • content/docs/standalone/main/documentation/mcp/guardrails/_index.md (editable here)
  • content/docs/standalone/main/documentation/mcp/guardrails/about.md (editable here)
  • content/docs/standalone/main/documentation/mcp/guardrails/setup.md (editable here)
  • content/docs/standalone/main/documentation/mcp/mcp-authn.md (editable here)
  • content/docs/standalone/main/documentation/mcp/mcp-authz.md (editable here)
  • content/docs/standalone/main/documentation/mcp/mcp-observability.md (editable here)
  • content/docs/standalone/main/documentation/mcp/mcp-target-policies.md (editable here)
  • content/docs/standalone/main/documentation/mcp/spec-compatibility.md (editable here)
  • content/docs/standalone/main/integrations/mcp/_index.md (editable here)
• Reference regenerated by: agentgateway/website .github/workflows/reference-docs.yaml

agentgateway/agentgateway#3601 — mcp: expose list/* results into CEL

• Product: agentgateway (upstream) → agentgateway/website
• Docs version: standalone/main and kubernetes/main

agentgateway/agentgateway#3601 exposes terminal MCP list responses to post-request CEL. Readers can now add list/* response payloads to access logs, traces, and metrics with mcp.toolsList, mcp.promptsList, mcp.resourcesList, and mcp.resourceTemplatesList. Before this change, the MCP observability docs described post-request tool-call payloads only, while list/* payloads were absent. The generated CEL reference covers the raw fields, and these docs now explain the policy phase and standalone access-log usage.

How agentgateway-3601 was drafted, and what was not verified

agentgateway/agentgateway#3601 — mcp: expose list/* results into CEL

• Code PR: mcp: expose list/* results into CEL agentgateway#3601
• Code issue: none linked
• Product: agentgateway (upstream) → agentgateway/website
• Docs version: standalone/main and kubernetes/main
• Category: scoped-edit / pr

Plan, and what changed it

• Planned: Document the new post-request MCP list result variables on the CEL variables pages and the standalone MCP observability workflow.
• Learned: pr-triage-worklist-agentgateway-3601.json authorized no Kubernetes MCP observability page and no create_in directory, so Kubernetes coverage belongs on the CEL variables reference page.
• Did: Added the list result field reference to both mode trees, added the standalone access-log example, and wrote a proposed release note.

Why a documentation change is necessary

The pull request adds mcp.toolsList, mcp.promptsList, mcp.resourcesList, and mcp.resourceTemplatesList to the MCP CEL context after terminal list/* responses. The existing standalone MCP observability page documented post-request mcp.tool.* fields for tool calls, but did not describe list result fields or show how to add them to access logs. The CEL variables pages explained which top-level variables are available by policy type, but did not explain that mcp now carries list response payloads only after the MCP server responds.

What changed on disk

• content/docs/standalone/main/reference/cel/variables.md: Added a phase-specific table for MCP list result variables.
• content/docs/kubernetes/main/reference/cel/variables.md: Added the same MCP list result variable table for the Kubernetes tree.
• content/docs/standalone/main/documentation/mcp/mcp-observability.md: Added an access-log example for tools/list results and a method-to-variable table.
• .pr-triage/agentgateway-3601/proposed-release-note.md: Added a New features note under the shared Operations area.

How to verify this change

1. In the standalone MCP observability guide, add the documented frontendPolicies.accessLog block with filter: 'mcp.methodName == "tools/list"' and add.tools: 'mcp.toolsList', then run the existing agentgateway -f config.yaml command.
2. Connect to the MCP target from the agentgateway playground so that the client sends tools/list, then check stdout for an access log field named tools that contains the terminal tools list response.
3. In both documentation modes, open the CEL variables page and verify that mcp.toolsList, mcp.promptsList, mcp.resourcesList, and mcp.resourceTemplatesList match the generated CEL reference fields for mcp.

Proposed release note

Wrote .pr-triage/agentgateway-3601/proposed-release-note.md because the pull request changes observable post-request CEL behavior. The note uses the Operations area because both standalone and Kubernetes development release-note pages have that area.

Style review

Ran the structure, STE, reread, product-specific, shortcode, and hard-refusal passes plus git diff --check, positional-language grep, bare-kind grep, and doc-test/rebase literal greps. One finding, applied: split the new phase description so the authorization and post-request behaviors are separate sentences.

What was not verified

The configuration was not applied to a cluster, so every command in this diff is unrun. The work-list recorded test_env.state: unconfigured; docs-setup-env would be needed to stand up an environment. The generated CEL reference workflow was not run here, so the docs were checked against the dossier diff rather than generated site output.

Draft branch: pr-tracker-draft-agentgateway-3601

---

Important

The test suite has not run on this pull request. It was opened by github-actions[bot], and GitHub does not start workflows for pull requests opened with the repository's own token. Doc tests, link checking and the static checks are held as action_required until somebody presses Approve and run on the Checks tab. Cloudflare Pages and DCO are GitHub Apps rather than Actions, so those two do run on their own.

Please approve the checks before reviewing the content: an absence of failures here means the tests have not run, not that they passed.

[cloudflare-workers-and-pages]

Deploying agentproxy with    Cloudflare Pages

Latest commit:	56dc32e
Status:	⚡️  Build in progress...

View logs