# VPC Service Controls (service perimeters): what it can block and where it stops

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

VPC Service Controls (service perimeters) is a Google Cloud mechanism. A service perimeter creates a security boundary around Google Cloud resources. It applies to google Cloud managed services and the projects in the perimeter; Google says it does not block access to third-party APIs or services on the internet.

A service perimeter creates a security boundary around Google Cloud resources. It allows free communication within the perimeter but, by default, blocks communication to Google Cloud services across it.

A service perimeter creates a security boundary around Google Cloud resources. It allows free communication within the perimeter but, by default, blocks communication to Google Cloud services across it. It applies to Google Cloud managed services and the projects in the perimeter.

Limits: not all Google Cloud services are supported, the perimeter does not block third-party APIs or services on the internet, and changes can take up to 30 minutes to propagate and may briefly block requests. Dry run mode logs requests that violate the perimeter policy without denying them. 1 library entry, a service perimeter around managed services, uses it.

## Documented limits

- Not all Google Cloud services are supported. ([source](https://cloud.google.com/vpc-service-controls/docs/overview))
- The perimeter does not block third-party APIs or services on the internet. ([source](https://cloud.google.com/vpc-service-controls/docs/overview))
- Changes can take up to 30 minutes to propagate and may briefly block requests. ([source](https://cloud.google.com/vpc-service-controls/docs/create-service-perimeters))

## Testing before enforcement

Dry run mode logs requests that violate the perimeter policy without denying them. ([source](https://cloud.google.com/vpc-service-controls/docs/dry-run-mode))

## The 1 library entry written in it

- [Service perimeter around managed services](/guardrails/gcp-vpcsc-service-perimeter/): Google Cloud, VPC Service Controls (service perimeters), data exfiltration

**Where Act is behind.** Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

## Related pages

- [Principal access boundary (PAB) policies: how it works, its limits and how to test it](/mechanisms/principal-access-boundary/)
- [Service control policies (SCPs): how it works, its limits and how to test it](/mechanisms/scp/)
- [Resource control policies (RCPs): how it works, its limits and how to test it](/mechanisms/rcp/)

## Sources

- VPC Service Controls (service perimeters): https://cloud.google.com/vpc-service-controls/docs/overview (read 10 Nov 2026)
- Limit: https://cloud.google.com/vpc-service-controls/docs/create-service-perimeters (read 10 Nov 2026)
- Testing: https://cloud.google.com/vpc-service-controls/docs/dry-run-mode (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/mechanisms/vpc-service-controls/
