docs/root/configuration/advanced/well_known_dynamic_metadata.rst
.. _well_known_dynamic_metadata:
Filters can emit dynamic metadata via the setDynamicMetadata routine in the
:repo:StreamInfo <envoy/stream_info/stream_info.h> interface on a
:repo:Connection <envoy/network/connection.h>. This metadata emitted by a filter can be
consumed by other filters and useful features can be built by stacking such filters. For example,
a logging filter can consume dynamic metadata from an RBAC filter to log details about runtime
shadow rule behavior. Another example is where an RBAC filter permits/restricts MySQL/MongoDB operations
by looking at the operational metadata emitted by the MongoDB filter.
The following Envoy filters emit dynamic metadata that other filters can leverage.
External Authorization Filter <config_http_filters_ext_authz_dynamic_metadata>External Authorization Network Filter <config_network_filters_ext_authz_dynamic_metadata>Header-To-Metadata Filter <config_http_filters_header_to_metadata>JWT Authentication Filter <config_http_filters_jwt_authn> for the extracted
:ref:header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>
and :ref:payload <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>Mongo Proxy Filter <config_network_filters_mongo_proxy_dynamic_metadata>MySQL Proxy Filter <config_network_filters_mysql_proxy_dynamic_metadata>Postgres Proxy Filter <config_network_filters_postgres_proxy_dynamic_metadata>Role Based Access Control (RBAC) Filter <config_http_filters_rbac_dynamic_metadata>Role Based Access Control (RBAC) Network Filter <config_network_filters_rbac_dynamic_metadata>ZooKeeper Proxy Filter <config_network_filters_zookeeper_proxy_dynamic_metadata>MCP Filter <config_http_filters_mcp>.. _config_http_filters_mcp_dynamic_metadata:
The :ref:MCP filter <config_http_filters_mcp> emits the following dynamic metadata under the
envoy.filters.http.mcp namespace when processing MCP (Model Context Protocol) JSON-RPC requests:
.. csv-table:: :header: Name, Type, Description :widths: 1, 1, 4
method, string, "The JSON-RPC method name (e.g., initialize, tools/list, tools/call)."
id, number, "The JSON-RPC request ID."
params, struct, "The params object from the JSON-RPC request containing method-specific parameters."
This metadata is consumed internally by the :ref:MCP router filter <config_http_filters_mcp_router> for
request routing and aggregation. It can also be used by other filters such as RBAC for policy enforcement
or access logging.
The following Envoy filters can be configured to consume dynamic metadata emitted by other filters.
External Authorization Filter via the metadata context namespaces <envoy_v3_api_field_extensions.filters.http.ext_authz.v3.ExtAuthz.metadata_context_namespaces>RateLimit Filter limit override <config_http_filters_rate_limit_override_dynamic_metadata>Original destination listener filter <config_listener_filters_original_dst>TLS Inspector listener filter <config_listener_filters_tls_inspector_dynamic_metadata>.. _shared_dynamic_metadata:
Dynamic metadata that is set by multiple filters is placed in the common key namespace envoy.common. Refer to the corresponding rules when setting this metadata.
.. csv-table:: :header: Name, Type, Description, Rules :widths: 1, 1, 3, 3
access_log_hint, boolean, Whether access loggers should log the request., "When this metadata is already set: A true value should not be overwritten by a false value, while a false value can be overwritten by a true value."
The following Envoy filters emit shared dynamic metadata.
Role Based Access Control (RBAC) Filter <config_http_filters_rbac_dynamic_metadata>Role Based Access Control (RBAC) Network Filter <config_network_filters_rbac_dynamic_metadata>The following filters consume shared dynamic metadata.
Metadata Access Log Filter<envoy_v3_api_msg_config.accesslog.v3.MetadataFilter>