Permissions and Security

Permissions

The MCP server acts as you. Every tool call is checked against your Stackless roles, schema access, and dashboard access, exactly as if you were using the Stackless app:

• Tool discovery is permission-aware. Your client only sees the tools your roles allow. After an administrator changes your roles, reconnect so the client refreshes its tool list.
• Warehouse queries are read-only and limited to the schemas your roles can access.
• Ownership still applies. You can only change drafts, schedules, and Monitors you own or are allowed to manage.

Confirmations

Tools that make consequential changes are guarded. Your client must show you the action and send an explicit confirmation before Stackless runs it. Guarded actions include:

• Publishing models and dashboards, refreshing or unpublishing models, and deleting drafts.
• Cancelling runs.
• Creating, changing, pausing, or deleting scheduled dashboard exports.
• Pausing, resuming, syncing, rescheduling, activating, or changing the schema of source connectors.
• Changing or test-sending Operations failure alerts.

Review generated queries, model changes, dashboards, and other write actions before approving them. AI agents can make mistakes, so verify important results against the underlying Stackless asset.

Reliable changes

Every change carries an idempotency key, so a retried request cannot apply the same change twice. Longer operations, such as publishes and refreshes, return an operation that the client checks until it completes, fails, or is cancelled.

Data handling

When you use the MCP server, your agent or client sends the tool request and its arguments to Stackless. Stackless returns the requested tool result to that client. The MCP connection does not give the client unrestricted access to your warehouse, and Stackless continues to enforce role-based access and ownership.

Do not use the MCP server for data that your organization prohibits from being shared with its approved AI provider. Your use of the agent or client is also subject to your organization's policies and that provider's terms. See the Stackless Privacy Notice for Stackless data-processing information.

Sessions

Connections use short-lived access tokens that the client refreshes in the background. Signing out of Stackless revokes your MCP sessions. Removing a user's roles or deleting the user revokes theirs.