# Security

> Least-privilege scopes, read-only mode, service accounts for agents, reviewing agent tasks, revoking access and what is logged.

**What this is:** how to give an AI client exactly the access it needs, and see what it did. **When you need it:** before you connect an agent to a real organization.

1.  Approve only the scopes the client needs.
2.  Switch on read-only for clients that only look.
3.  Run unattended agents as a service account.
4.  Review what agents create before it lands.

## Least privilege

The client can do only what its [scopes](https://docs.taskadence.com/guides/authentication/#scopes) allow, and never more than you can. An assistant that answers questions needs `tasks:read` alone. Destructive tools require `admin` — don’t grant it to an agent unless that is the job.

## Read-only mode

Switch on **Read-only** in the app’s MCP generator and the connection offers no write tools. The server enforces it, not only the configuration text.

## Service accounts for agents

An agent that runs on its own should act as a **service account** — a member of your organization that cannot sign in — with its own token, restricted to the projects it works in. Its changes are then attributed to it, and it keeps working when people leave. Mint its token in [Developers → Tokens](https://taskadence.com/developers?dev=tokens).

## Agent tasks are reviewed

A task created through MCP, the API or the SDK (scripts included) carries a robot mark; **Filter → Created By → Agents** finds them.

By default an agent cannot put a task into a **private project**: the task is created with no project, marked **Needs review**, and held on its team’s **List** under **No project → Agent tasks**.

Someone who may edit it decides, from **Review…** in its row menu or the bar atop the task:

-   **Accept:** it becomes ordinary work, moved into the private project (you need edit rights there).
-   **Reject:** it is archived where it is. Nothing is deleted.

An agent cannot accept its own task.

What an agent creates waits for a person

**The review list** is any task list filtered to **Review → Needs review**: My Tasks, the team’s List, the project’s. **The setting**, for owners and admins, is **Settings → General → Tasks created by agents**: private projects only (default), every agent task, or never.

## Revoking access

-   **An OAuth connection:** revoke it on the Developers page; the client’s session ends.
-   **A token:** revoke it in Developers → Tokens. It stops working at once and answers [`token-revoked`](https://docs.taskadence.com/guides/errors/). Rotate tokens you keep.

## What is logged

-   Every tool call, in your organization’s events, with the token’s name.
-   The agent’s name on each change: the token’s, or the connected app’s (Claude Code), beside the person.
-   Token events — minted, rotated, revoked — in the audit log.

---
Source: https://docs.taskadence.com/mcp/security/