Give your agent access.
Define what it can do.
A useful agent needs business data and execution tools. Start with authorized accounts, a defined workspace, and explicit boundaries for the work you want it to perform.
An authorized account
The documented MCP connection uses OAuth. Your agent connects as the account that authorizes Siftree access, rather than receiving a universal view of every workspace.
Start by confirming which account and workspace the agent is using.
Workspace-scoped discovery
The MCP tools list the channels an authenticated account can reach. Dataset, document, task, and report operations take a channel identifier.
Review the accessible workspace and sources before running a task.
Inspectable execution
The documented tools expose authoring-session status, task runs, and run logs. Cancellation tools can stop supported builds, workflows, and queued or running tasks.
Cancellation does not undo changes a run has already committed.
These behaviors are described in the Siftree MCP reference. Confirm the configuration and control requirements for your deployment with the team.
Scope the data.
Scope the actions.
A research workflow and a workflow that changes customer records have different operating requirements. Agree on the permissions and review points for each step.
Bring us your review checklist- Source access
- Which accounts, providers, data fields, and read or write operations does this workflow require?
- Data handling
- Where will inputs and outputs be stored, which providers receive them, and what retention, deletion, or residency requirements apply?
- Execution
- What runtime isolation, network access, secret handling, resource limits, and review steps are required?
- Team access
- Who may view source records, inspect reports, change tasks, or authorize external actions?
- Operations
- Who handles failed runs, source changes, access revocation, and any required audit evidence?
Understand the data policy.
Our privacy policy describes personal information collection, processing, retention, security measures, and privacy requests. Confirm your workflow’s business-data and provider requirements during evaluation.
Match the requirements to the deployment.
If you require particular certifications, encryption specifications, isolation guarantees, data regions, contractual terms, or incident-response commitments, request the relevant documentation from the team. Availability and scope should be established before production use.
Request a security discussion →Practical security questions.
Does connecting an agent give it access to every workspace?
The documented connection is authorized through a Siftree account. Workspace discovery lists the channels that authenticated account can reach. Confirm the account, workspace, and source access before running work.
Can a workflow change data in connected apps?
Some integrations support actions as well as reads. Specify allowed actions and review requirements during workflow setup, and check the actual connector and account permissions before enabling writes.
Can I stop a running task?
The MCP reference includes cancellation tools for authoring sessions, task runs, and workflows. Cancellation stops supported pending or running work but does not roll back changes already committed.
Where can I confirm certifications or specific security controls?
Contact the team with the requirements for your use case. This page describes the documented access and execution model; it does not establish a certification, region, or deployment-specific control.