Hi Vercel team,

Could you clarify the supported, least-privilege way to inspect project and integration settings through Vercel MCP before making reversible deployment changes?

Observed on 8 November 2026, after completing the supported team-consent flow:

• Project listing and individual project reads succeeded on the existing MCP connection.
• list_integration_configurations with a project view and explicit team returned HTTP 403 for integrationConfiguration, without requesting reauthentication.
• Successful get_project and list_projects responses omitted rootDirectory, Git production-branch details and previewDeploymentsDisabled.

We need to observe the actual current settings and connected resource behaviour before choosing a reversible control. Missing fields cannot establish the previous values needed for rollback. No alternate credentials or permission changes have been used to work around the denied read.

Could a Vercel staff member confirm:

1. Is there a supported read-only MCP permission/tool path for these settings? If not, what precisely scoped, officially supported read-only route is required, and where is it documented?
2. Are the omitted project fields intentionally excluded from MCP responses, and is there a supported way to request the complete configuration?
3. Does previewDeploymentsDisabled prevent deployment creation before deployment lifecycle webhooks and integration resource provisioning, such as preview database branches? Are there integration-specific exceptions?

The Vercel Support assistant referred this MCP question to Community on 14 November. We are seeking documentation or staff confirmation rather than treating an AI-generated answer as a verified deployment guarantee.

This post deliberately excludes account/team/project identifiers, request IDs, credentials, source code and logs. We are not requesting a permission bypass, project deletion, production pause or a paid upgrade.

Thank you.