Google's Agent Registry release notes announce Preview support for MCP tool protocol metadata on November 19, 2026. The dated change includes policy hints for tool enablement and human approval, plus provider metadata.
The preview gives policy hints a defined location
The official JSON schema separates predefined behavioral annotations from extensible metadata under _meta. Google's com.googleapis.iap/PolicyHints namespace includes tool disablement and human-approval modes. The documentation says IAP and Agent Gateway evaluate these hints.
When the tool-disabled field is omitted, its documented default is false. Approval modes distinguish disabled, always and conditional approval. These details describe this integration; they do not establish that arbitrary MCP clients enforce Google-specific metadata.
Inspect the path that invokes the tool
Engineering interpretation: a discovery record can make the intended rule visible, while the component executing a call determines whether that rule takes effect. Reviewing only the registry entry would leave an important part of the system unobserved.
For a testable design, retain the requested arguments, the approval decision and an independent indication of whether the tool ran. A visible prompt alone would not establish that a rejected call was prevented.
A proposed gateway approval test
Original exercise, not executed: define synthetic read_fixture and replace_fixture tools. Configure mandatory approval for replacement and invoke it through the intended gateway. Reject the request, then inspect a counter maintained by the mock tool to determine whether execution occurred.
Repeat through a direct client with the same metadata. Document which component applies the rule instead of assuming identical enforcement. The exercise would test the chosen invocation paths; it would not demonstrate universal MCP behavior or production readiness of the preview.
Sources accessed November 21, 2026. Views are my own and do not represent any employer, past or present.
Sources and evidence
Check that the component invoking each tool enforces its approval metadata, especially when a direct client can take another path.