# MCP server security on AWS, Azure and Google Cloud

URL: https://mcpservercybersecurity.com/guides/mcp-server-security-on-aws-azure-and-google-cloud/
Updated: 2026-11-16

AWS, Azure and Google Cloud each document a way to put authentication in front of a hosted MCP server: a JWT authorizer on AgentCore Runtime, key and Entra ID token validation in API Management, and IAM invoker access on Cloud Run. Audience checks, scopes, egress and logging remain the customer's job. Sources were read on 16 Nov 2026.

## What do cloud providers offer for hosted MCP servers?

Each provider documents an authentication layer in front of the server. On AWS, the AgentCore Runtime guide deploys an MCP server and its example configures a CUSTOM_JWT authorizer with an OpenID discovery URL and a list of allowed clients, and passes the Authorization header through to the runtime.

On Azure, API Management can expose and govern MCP servers and secure inbound access (client to API Management) and outbound access (API Management to the server). Inbound options include a subscription key and OAuth 2.1 tokens issued by Microsoft Entra ID, validated with the validate-azure-ad-token policy. On Google Cloud, a Cloud Run service requires the Cloud Run Invoker IAM role by default, and the documentation lists IAM invoker permission, OIDC ID tokens and Identity-Aware Proxy as ways to authenticate clients.

Sources: [AWS documentation: Deploy MCP servers in AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html); [Microsoft Learn: Secure access to MCP servers in Azure API Management](https://learn.microsoft.com/en-us/azure/api-management/secure-mcp-servers); [Google Cloud documentation: Host MCP servers on Cloud Run](https://cloud.google.com/run/docs/host-mcp-servers).

## Which settings are the customer's job?

The audience, the scopes, the network path and the logs stay with you. The MCP authorization specification requires the server to validate that each token was issued for it, so confirm that the provider's authorizer checks the audience you intend, and keep a check in server code as defense in depth.

Scopes are yours too. OWASP advises narrow, per-server credentials and short-lived tokens, and Azure's guidance on subscription keys is to store them in workspace settings or secure inputs rather than in the configuration file.

Network exposure is also a choice you make. A Cloud Run service can be opened to the public, and API Management can front an MCP server hosted outside it, so confirm which path a client actually takes before you describe the server as protected.

Sources: [MCP specification: Authorization (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization); [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html); [Microsoft Learn: Secure access to MCP servers in Azure API Management](https://learn.microsoft.com/en-us/azure/api-management/secure-mcp-servers).

## How do local clients authenticate to a remote server?

Use the platform identity the provider documents and avoid sharing static secrets. Google's documentation shows running a local Cloud Run proxy so the MCP client reaches the remote service using your own credentials and the invoker role, rather than opening the service to the public.

For clients that must use OAuth, follow the authorization specification: the client sends the resource parameter, and the server answers an invalid or expired token with 401.

Rotate any shared secret on a schedule and prefer short-lived tokens, as OWASP advises over long-lived personal access tokens.

Sources: [Google Cloud documentation: Host MCP servers on Cloud Run](https://cloud.google.com/run/docs/host-mcp-servers); [MCP specification: Authorization (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization).

## What should you check before a hosted server is reachable?

Check that authentication is on, that the server cannot be tricked into reaching internal addresses and that it validates Origin. The MCP security best practices describe server-side request forgery against addresses such as the 169.254.169.254 cloud metadata endpoint and advise blocking private and link-local ranges, requiring HTTPS and using an egress proxy for server-side deployments.

Avoid writing the IP validation yourself, because custom parsers miss encoded forms; use a maintained library or an egress proxy.

Sources: [MCP specification: Security Best Practices (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices); [MCP specification: Transports (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/transports).

## What should a hosted server log?

Log every tool invocation with parameters, the caller's identity and a timestamp, and send the records to your SIEM. OWASP also asks for redaction of secrets and personal data before storage.

Log at the MCP server, not only at the cloud front door: the specification notes that downstream logs can show a different identity than the real caller when tokens are passed through.

Cloud audit logs show who reached the service and not which tool ran with which arguments, so the application log is still needed.

Sources: [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html); [MCP specification: Security Best Practices (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices).

## Sources

- [AWS documentation: Deploy MCP servers in AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html) (docs.aws.amazon.com), read 2026-11-16
- [Microsoft Learn: Secure access to MCP servers in Azure API Management](https://learn.microsoft.com/en-us/azure/api-management/secure-mcp-servers) (learn.microsoft.com), read 2026-11-16
- [Google Cloud documentation: Host MCP servers on Cloud Run](https://cloud.google.com/run/docs/host-mcp-servers) (cloud.google.com), read 2026-11-16
- [MCP specification: Authorization (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization) (modelcontextprotocol.io), read 2026-11-16
- [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html) (cheatsheetseries.owasp.org), read 2026-11-16
- [MCP specification: Security Best Practices (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices) (modelcontextprotocol.io), read 2026-11-16
- [MCP specification: Transports (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/transports) (modelcontextprotocol.io), read 2026-11-16

## Related pages

- [MCP Security vs API Security: What Changes](/guides/mcp-security-vs-api-security/)
- [MCP Audit Logging: What to Record and How Long to Keep It](/guides/mcp-audit-logging-what-to-record/)
- [SSRF (glossary)](/glossary/ssrf/)
- [Resource indicators (glossary)](/glossary/resource-indicators/)
- [All guides](/guides/)
- [MCP Server Scanning and Testing: Tools and Limits](/guides/mcp-server-scanning-and-testing/)
- [Securing a Python MCP Server: Host Checks and Deployment](/guides/securing-a-python-mcp-server/)
- [The ranking](/ranking/)
- [Glossary](/glossary/)
