Useful access. Clear boundaries.

Permission checks on requests

Authentication, workspace membership and connection permissions are checked on the server. Connecting through MCP does not bypass them.

Access you choose

Assistant grants are scoped to a connection and its permitted operations. Start with read-only access and revoke grants when an assistant no longer needs them.

Encrypted stored credentials

Business credentials are encrypted and scoped to their workspace and connection. They do not belong in the website, your enquiry or a prompt pasted into an assistant.

Operations have recorded intent and outcome. If a mutating request might have reached the provider but its result is unknown, MCP XYZ does not automatically repeat it. The outcome needs to be reconciled before replay.

This matters because “try again” can mean two orders or two changes when the first request actually succeeded. A timeout alone is not proof that nothing happened.

Your AI assistant and software provider have their own permissions, policies and data handling. Authorised results can be returned to the assistant you connect. Review those services before sharing sensitive information.

Removing a local grant blocks that grant in MCP XYZ. It does not necessarily revoke the provider’s token remotely. A selected Procore company is not a universal boundary for global endpoints available to the authorised principal.

Connection and authentication tests are not proof of a live business workflow. Unleashed workflows await validation; Procore also needs applicable provider approval and live acceptance.

Contact Jiffi with the affected page or connection, what you observed and when it happened. Please leave credentials, private records and active tokens out of the message.