Request is prohibited by organization's policy — VPC Service Controls perimeter violation
A VPC Service Controls perimeter blocked the API call because the caller is outside the perimeter or not covered by an access level.
Request is prohibited by organization's policyVPC Service Controls: Request is prohibited by organization's policy. vpcServiceControlsUniqueIdentifier Meaning
Look at the audit log's VPC_SERVICE_CONTROLS violation (unique id), then add an ingress/egress rule or access level for the caller (service account, IP range), or run the call from inside the perimeter. Use dry-run mode first.
Common causes
- Caller outside the perimeter
- Missing ingress/egress rule
- Cross-project resource not in the perimeter
- Console/CLI access from a non-allowed network
- Service not allowed in the restricted API list
⚡ Quick fix
- Find the violation in Logs Explorer (
protoPayload.metadata.violationReason) - Add an ingress/egress rule or access level
- Test with dry-run before enforcing
Detailed fix by platform
Shell
gcloud logging read 'protoPayload.metadata."@type"="type.googleapis.com/google.cloud.audit.VpcServiceControlAuditMetadata"' --limit=5
How to diagnose
- Violation ID — Found?
- Caller — Inside perimeter?
- Rule — Needed?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 15281 SQL Server Msg 15281: SQL Server blocked access to procedure 'sys.xp_cmdshell' (component 'xp_cmdshell' turned off)
- AADSTS50053 AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity
- App Check Firebase App Check: requests rejected (403 / app-check-token-is-invalid / attestation failed)
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026