MCP servers

Related topics

• allow policies secures MCP servers From the official documentation: “Identity and Access Management (IAM) [deny policies](/iam/docs/deny-overview) and [allow policies](/iam/docs/allow-policies) let you secure Google Cloud Model Context Protocol (MCP) servers.”
• Cloud Run works with MCP servers From the official documentation: “- [Host MCP servers on Cloud Run](/run/docs/host-mcp-servers).”
• Cloud Trace works with MCP servers From the official documentation: “For information about the Google Cloud MCP servers that generate traces and how to configure your application to instruct MCP servers to generate spans, see [Investigate MCP calls using Trace](/trace/docs/trace-remote-mcp-server-calls).”
• deny policies secures MCP servers From the official documentation: “Identity and Access Management (IAM) [deny policies](/iam/docs/deny-overview) and [allow policies](/iam/docs/allow-policies) let you secure Google Cloud Model Context Protocol (MCP) servers.”
• MCP servers is part of Knowledge Catalog From the official documentation: “Model Context Protocol (MCP) servers in Knowledge Catalog (formerly Dataplex Universal Catalog) let you connect AI agents and developer tools to your catalog metadata and data lineage.”
• Model Armor secures MCP servers From the official documentation: “To enable Model Armor, complete the steps in [Configure Model Armor protection for Google and Google Cloud MCP servers](/model-armor/model-armor-mcp-google-cloud-integration).”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• deny policies is part of Identity and Access Management From the official documentation: “The following attributes can be used in your Identity and Access Management deny policies:”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• allow policies is part of Identity and Access Management From the official documentation: “The following attributes can be used in your Identity and Access Management allow policies:”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Cloud Trace From the official documentation: “To identify requests with high latency using Cloud Logging, apply the `traceSampled=true` filter to correlate logs in Cloud Logging with traces in Cloud Trace.”
• Cloud Logging works with Knowledge Catalog From the official documentation: “Knowledge Catalog sends logs for service operations and job executions to Cloud Logging.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Model Armor From the official documentation: “This graph uses the metrics that Model Armor publishes to Cloud Monitoring.”
• Cloud Storage works with Knowledge Catalog From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with Cloud Trace From the official documentation: “To create an alerting policy that triggers if there are errors exporting [Cloud Trace](/trace/docs) data to BigQuery, use the following settings.”
• Cloud Audit Logs secures BigQuery From the official documentation: “For BigQuery, [Cloud Audit Logs](/logging/docs/audit) is used for both data access logs and audit logs, which are enabled by default.”
• Cloud Audit Logs works with Cloud Logging From the official documentation: “- For real-time analysis, alerting, and visualization, stream the audit logs to [Logging](/logging/docs/overview).”
• Cloud Audit Logs works with Cloud Run From the official documentation: “The sample code shows you how to read Cloud Storage events using Cloud Audit Logs in a service deployed to Cloud Run.”
• Cloud Audit Logs works with Cloud Trace From the official documentation: “Cloud Audit Logs for Cloud Trace let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Audit Logs works with Knowledge Catalog From the official documentation: “Cloud Audit Logs for Knowledge Catalog let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Audit Logs works with Model Armor From the official documentation: “Model Armor uses audit logs to record administrative and resource management activities.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging is an alternative to Cloud Trace From the official documentation: “You can use Cloud Trace or Cloud Logging to understand how long a particular request has taken.”
• Cloud Logging works with Model Armor From the official documentation: “Use Cloud Logging to analyze Model Armor usage patterns, errors, and performance metrics.”
• Cloud Monitoring works with Knowledge Catalog From the official documentation: “Cloud Logging and Cloud Monitoring let you track billable token consumption for Knowledge Catalog (formerly Dataplex Universal Catalog) data insights scans.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• Cloud Trace depends on Cloud Storage From the official documentation: “To determine the prompts and responses to display for a span, Cloud Trace issues queries to read log data and to read data stored in a Cloud Storage bucket.”
• Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
• Identity and Access Management secures Cloud Audit Logs From the official documentation: “IAM permissions and roles determine your ability to access audit logs data in the [Logging API](/logging/docs/reference/v2/rest), the [Logs Explorer](/logging/docs/view/logs-explorer-interface), and the [Google Cloud CLI](/logging/docs/reference/tools/gcloud-logging).”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management secures Cloud Trace From the official documentation: “Trace uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Model Armor From the official documentation: “Model Armor uses Identity and Access Management (IAM) to control access to resources.”
• Knowledge Catalog depends on Identity and Access Management From the official documentation: “Knowledge Catalog uses Identity and Access Management (IAM) for authorization.”
• Model Armor depends on Cloud Trace From the official documentation: “Because Model Armor widgets use observability spans to aggregate data, ensure that Cloud Trace is enabled for your agent runtimes.”
• Model Armor depends on Identity and Access Management From the official documentation: “Model Armor uses Identity and Access Management (IAM) to control access to resources.”