Skip to content

TaskLite MCP server

net.tasklite/mcptasklite.netstreamable-httpv0.14.4Scanned

tasklite.net: hosted backend, REST API and admin for apps built by AI agents

102 tools: 19 can delete or cancel things, 9 do something that can't be undone, 39 change things and 35 only read.

Tools: 19 delete, 9 irreversible, 39 write, 35 read.
  • Reads private data · 11
  • Reads text others write · 25
  • Can send data out · 13
  • 91 findings

Tools listed without sign-in. Remote posture

With Anlyon

19 tools here can delete or cancel things and 9 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TaskLite MCP server can do

The TaskLite MCP server is published by tasklite.net, a domain the MCP Registry verified. It has 102 tools. It can delete or cancel things (19 tools: delete_board, delete_project, delete_column, delete_item and 15 more), do things that cannot be undone, such as sending, paying or publishing (create_signature_request, configure_telephony_mapping, run_telephony_sync, send_test_push and 5 more) and create or change data (39 tools: configure_external_access, create_project, create_board, create_column and 35 more). 35 tools only read.

11 tools read private data (get_email_usage, get_cells, list_comments and 8 more); 25 tools bring in text other people can write (get_email_usage, list_comments, request_file_upload and 22 more); 13 tools can send data out of your system (add_comment, update_comment, create_signature_request and 10 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 91 findings (credentials-mention, long-description, annotation-conflict and base64-blob). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.14.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

102 tools

Deletes or cancels 19Claude Code: deny
  • delete_app_endpointDelete an endpoint of an app for good: /apps/{appSlug}/api/{slug} stops answering at once and the endpoint cannot be brought back (create it again with create_app_endpoint).1 finding

    Why it is in this group

    • The name "delete_app_endpoint" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Delete an endpoint of an app for good: /apps/{appSlug}/api/{slug} stops answering at once and the endpoint cannot be brought back (create it again with create_app_endpoint). The board and its rows are not touched. Confirm with the user first: a frontend that calls this endpoint breaks. To take an endpoint offline and keep its definition, use update_app_endpoint with isActive false instead (list_app_endpoints shows active endpoints only, so keep the id). Get the endpoint id from list_app_endpoints.

    Annotations the server declares

    • title: Delete app endpoint
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_app_roleDelete a business role of an app's project.1 finding

    Why it is in this group

    • The name "delete_app_role" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Delete a business role of an app's project. Check first with list_app_role_grants who holds it and with get_board_policy where policies still name it: a policy that names a role that no longer exists simply matches nobody. Requires organization owner or admin.

    Annotations the server declares

    • title: Delete an app role
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_boardDelete a board with every item on it.No findings

    Why it is in this group

    • The name "delete_board" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a board with every item on it. Destructive and not undoable, confirm with the user first, and prefer delete_column when only part of the model is wrong.

    Annotations the server declares

    • title: Delete board
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_board_policyRemove a board's access policy.1 finding

    Why it is in this group

    • The name "delete_board_policy" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Remove a board's access policy. An endpoint of that board in rowLevelSecurity mode "policy" then has no policy to follow; check what it allows afterwards with explain_access before leaving it on a live app. Requires organization owner or admin.

    Annotations the server declares

    • title: Remove a board's access policy
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_columnDelete a column and every value stored in it.No findings

    Why it is in this group

    • The name "delete_column" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a column and every value stored in it. Destructive, confirm with the user first. Use update_column when the column is right but its name, type or options are wrong.

    Annotations the server declares

    • title: Delete column
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_commentDelete a comment from an item thread.No findings

    Why it is in this group

    • The name "delete_comment" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a comment from an item thread. Destructive, confirm with the user before calling. Needs projectId, itemId and the commentId.

    Annotations the server declares

    • title: Delete a comment
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_itemDelete an item.No findings

    Why it is in this group

    • The name "delete_item" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete an item. Destructive, confirm with the user before calling.

    Annotations the server declares

    • title: Delete item
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_projectDelete a project with every board, column and row inside it.1 finding

    Why it is in this group

    • The name "delete_project" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Delete a project with every board, column and row inside it. Destructive: confirm with the user first, and name the project in the confirmation. The project goes to the organization recycle bin, so it can be restored from the admin until it is emptied.

    Annotations the server declares

    • title: Delete project
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • disconnect_telephonyRemove the phone system connection of an app: the stored token, the mapping and the record of which calls were written are deleted, and syncing stops.1 finding

    Why it is in this group

    • The description's first verb is "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Remove the phone system connection of an app: the stored token, the mapping and the record of which calls were written are deleted, and syncing stops. Rows already written to the board stay. Reconnecting later starts from start_telephony_connection and may write the recent calls again. Owner or admin of the app.

    Annotations the server declares

    • title: Remove a phone system connection
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • google_calendar_delete_eventDelete one event from a TaskLite calendar in the user's Google account.Reads text others write1 finding

    Why it is in this group

    • The name "google_calendar_delete_event" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Delete one event from a TaskLite calendar in the user's Google account. Deleting one already gone is not an error (alreadyGone true). notifyAttendees true emails its guests that it was cancelled.

    Annotations the server declares

    • title: Delete a calendar event
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • google_calendar_disconnectDisconnect the signed-in user's Google Calendar from TaskLite: the access is revoked at Google and forgotten here.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Disconnect the signed-in user's Google Calendar from TaskLite: the access is revoked at Google and forgotten here. Events already in the calendar stay where they are. Every app of this user stops writing to the calendar until it is connected again. Only when the person asked for it.

    Annotations the server declares

    • title: Disconnect Google Calendar
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • remove_app_userTake a person's access to an app away.1 finding

    Why it is in this group

    • The name "remove_app_user" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Take a person's access to an app away. Pass exactly one of two ids from list_app_users: userId, for someone who already signed in, switches them off (the same as set_app_user_role with isActive false: their calls are refused in every mode, nothing of theirs is deleted, and set_app_user_role or add_app_user switches them back on); pendingId, for a phone that add_app_user is still holding access for, cancels it, so that phone's first sign-in opens nothing. Requires organization owner or admin (an editor gets 403).

    Annotations the server declares

    • title: Take a person's app access away
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • revoke_app_inviteRevoke an invite code so nobody else can sign up with it.1 finding

    Why it is in this group

    • The name "revoke_app_invite" says "revoke": a word for removing or ending something.
    • The description says "Cannot be undone".
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Revoke an invite code so nobody else can sign up with it. People who already used it stay linked to their row and keep their access; to cut one of them off use unlink_app_user. Cannot be undone, create a new invite instead. Requires organization owner or admin. Get the invite id (not the code) from list_app_invites.

    Annotations the server declares

    • title: Revoke invite code
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • revoke_app_roleTake a business role away from an app user (a grant made with grant_app_role).1 finding

    Why it is in this group

    • The name "revoke_app_role" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Take a business role away from an app user (a grant made with grant_app_role). A role the user gets from the employees board (set_policy_identity) is not a grant: change the board row instead. Revoking a grant that does not exist also succeeds. Requires organization owner or admin.

    Annotations the server declares

    • title: Take an app role away from a user
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • set_app_user_roleChange what an existing user of an app may do, or switch them off or back on.1 finding

    Why it is in this group

    • The name "set_app_user_role" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Change what an existing user of an app may do, or switch them off or back on. Takes the userId from list_app_users and at least one of role and isActive. It also puts on the app's access list a user who is not on it yet (hasAccessRow false in list_app_users), which is what an endpoint in row-level security mode "shared" checks: use it for someone who already signed in and is refused with 403. isActive false switches the user off in every mode: their calls are refused until it is set back to true; nothing of theirs is deleted. For a person who has not signed in yet there is no userId: use add_app_user with their phone. Requires organization owner or admin (an editor gets 403).

    Annotations the server declares

    • title: Change an app user's role or switch them off
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • set_board_policySet who may read, write, create and delete rows of a board, and which columns, as a JSON document (a FULL REPLACE of the board's policy; read get_board_policy first to change part …2 findings

    Why it is in this group

    • The name "set_board_policy" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Info

      The description is 6,324 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...request before telling the user it is done. Requires organization owner or admin."

      What this check looks for
    Description, as the server wrote it
    Set who may read, write, create and delete rows of a board, and which columns, as a JSON document (a FULL REPLACE of the board's policy; read get_board_policy first to change part of one). It is enforced on the app's endpoints of this board whose rowLevelSecurity.mode is "policy" (create_app_endpoint / update_app_endpoint). Organization owners, admins and editors using the app are let through unless internalBypass is false. Fields: - schemaVersion: 1 (required). - internalBypass: default true. - rows.read / rows.write: a list of { roles, scope }. scope is "all", { "mine": "<column id>" } (rows whose column points at the caller: a relation to the row that stands for them, their verified phone or email, or a people column; add "via": "<relation column id>" for one more hop, or "via": ["<id>", "<id>"] for two, e.g. tenant -> apartment -> framework -> staff is { "mine": "<tenant.apartment>", "via": ["<apartment.framework>", "<framework.managers>"] }; each hop is a relation column of the board the step before points to, and the last one ends at the people board), { "created": true } (rows they created through the app) or { "where": CONDITION } (rows a condition selects, e.g. open cases older than 3 days, for an escalation view). A user gets the union of the rules that name any of their roles; no rule for their roles means no access. - rows.create / rows.delete: plain role lists. - columns: { "<column id or reserved field>": { "read": ACCESS, "write": ACCESS } }. ACCESS is a role list, or { "roles": [...], "orMine": "<column id>" } (these roles, or anyone for whom the row is theirs by that column). A column without an entry follows the row rules. An EMPTY list ("write": []) locks the column for everyone through the app: use it for assignedTo and for any field only an admin or an action may change. Reserved fields are title, description, status, priority, dueDate and assignedTo, addressed by those names. Reserved fields are open to anyone who may write the row unless you lock them, so lock assignedTo. - CONDITION (in where, rules.when): { "all": [c...] } | { "any": [c...] } | { "not": c } | a leaf { "col": "<column id or reserved field>", "op": OP, ... }. OP: eq / neq (with "value"), in (value is a list), empty, notEmpty, isMe (the column points at the caller; optional "via", one column id or a list of two), olderThan (col is updatedAt, createdAt or a date column; give "hours" or "days"), changed (this write sets col; only in rules). No free expressions. - rules: [{ "id", "when": CONDITION, "deny": { "write": "*" | [column ids], "except": [roles] }, "require": [column ids that must be filled after the write], "except": [roles], "message" }]. deny is judged on the row as it is BEFORE the write, require AFTER it. Rules bind people acting through the app; internal bypass users and an action's own columns are not held to deny. - actions: { "<name>": { "roles": [...], "input": { "<input name>": { "col": "<column id the value is written to>", "required": true } }, "set": { "<column id>": constant }, "event": "TRANSFER", "scope": "write" | "read", "approval": "<approval workflow id of the board>" } }. An action is role-gated, validates its input (an input without col is only data; "reason" is always accepted and goes to the history), writes its set and bound inputs in one transaction, and records event and reason in the history. It is the only way to change a column whose write is []. With approval it files a request for that workflow instead of writing; the write happens when the last step approves. Roles named by approval steps must exist (define_app_role). Actions run through the App API only (see below). Frontends run an action with POST /apps/<slug>/api/<endpoint>/<itemId>/actions/<name> and the inputs as the body; approvers read GET /apps/<slug>/api/me/approvals and answer POST /apps/<slug>/api/approvals/<requestId>/decide { "decision": "approve" | "reject", "comment"? }; GET /apps/<slug>/api/me/permissions lists the actions the caller may run as [{ name, allowed, roles, inputs, approval, event, scope }]. There is no MCP tool that runs an action. Roles are keys from list_app_roles, plus "*" (any signed-in user) and "public". Column ids come from get_board_schema. An invalid document is refused with POLICY_INVALID and an errors list naming each problem. Example (agents see and edit only their own cases, the manager sees and edits all, bookkeeping reads all, commission is visible to the owner, the manager and to the agent on his own rows): { "schemaVersion": 1, "rows": { "read": [ { "roles": ["owner","manager","bookkeeping"], "scope": "all" }, { "roles": ["agent"], "scope": { "mine": "<agent column id>" } } ], "write": [ { "roles": ["owner","manager"], "scope": "all" }, { "roles": ["agent"], "scope": { "mine": "<agent column id>" } } ], "create": ["owner","manager","agent"], "delete": ["owner"] }, "columns": { "<commission column id>": { "read": { "roles": ["owner","manager"], "orMine": "<agent column id>" }, "write": ["owner"] }, "<agent column id>": { "write": ["owner","manager"] }, "assignedTo": { "write": [] } }, "rules": [ { "id": "lock", "when": { "all": [ { "col": "<locked column id>", "op": "eq", "value": true } ] }, "deny": { "write": "*", "except": ["owner","manager"] }, "message": "The case is locked to its agent" } ], "actions": { "transfer": { "roles": ["owner","manager"], "input": { "agent": { "col": "<agent column id>", "required": true }, "reason": { "required": true } }, "set": { "<locked column id>": false }, "event": "TRANSFER" }, "unlock": { "roles": ["owner","manager"], "input": { "reason": { "required": true } }, "set": { "<locked column id>": false }, "event": "UNLOCK" }, "exception": { "roles": ["agent"], "input": { "reason": { "required": true } }, "set": { "<exception column id>": true }, "approval": "<workflow id, a role step>" } } } (The Achituv shape: a loc… [324 more characters not shown]

    Annotations the server declares

    • title: Set a board's access policy
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • void_signature_requestCancel a document that is out for signature: every link stops working.1 finding

    Why it is in this group

    • The name "void_signature_request" says "void": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Cancel a document that is out for signature: every link stops working. A completed document cannot be voided.

    Annotations the server declares

    • title: Cancel a signature request
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 9Claude Code: ask
  • check_invite_codeCheck whether an invite code works right now, the way an app does before sign-up (POST /auth/invites/check, the same public route, limited to 10 calls a minute per address).Can send data out1 finding

    Why it is in this group

    • The name "check_invite_code" says "invite": a word for sending, and what is sent cannot be taken back.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "check_invite_code" says "invite": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "check_invite_code" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_invite_code" says "invite": a word for sending, and what is sent cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Check whether an invite code works right now, the way an app does before sign-up (POST /auth/invites/check, the same public route, limited to 10 calls a minute per address). A working code answers { valid: true, organizationId, app: { name, slug }, label, expiresAt }; anything else (unknown, revoked, expired, used up, its row deleted, its app switched off or deleted) answers only { valid: false }, with no reason, by design. It does not use the code up. For the reason a code stopped working, read its status in list_app_invites.

    Annotations the server declares

    • title: Check an invite code
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • configure_telephony_mappingSay where the calls go: the board that receives one row per call, which column gets which call field, and, optionally, how a call is linked to a customer (by the other party's phon…Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.columns.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.columns.to): what the tool writes goes there.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Say where the calls go: the board that receives one row per call, which column gets which call field, and, optionally, how a call is linked to a customer (by the other party's phone number, Israeli numbers compared in one normal form: 05x, +9725x, 9725x) and to an employee (by the extension number). Replaces the whole mapping. Column ids from get_board_schema; the boards must be in the app's project. Call fields: externalId (the PBX call id, map it to keep rows traceable), direction, from, to, extension, agentName, startedAt, answeredAt, endedAt (ISO UTC times, use date/datetime columns), durationSec, talkSec (numbers), status, hangupBy. direction and status are written as Hebrew words (נכנסת/יוצאת, נענתה/לא נענתה/תפוס/נכשלה); for a dropdown or status column whose options differ, set labels. customer: { boardId (the customers board), matchColumnId (its phone column), linkColumnId (a relation column on the calls board) }. employee: the same with the extension column of the employees board. A phone or extension that two rows share is not linked (never guessed). startDate (YYYY-MM-DD) is where the first sync starts, default 7 days back. Syncing happens in the background once the server runs the telephony worker; run_telephony_sync does it now. Owner or admin of the app.

    Annotations the server declares

    • title: Map calls to a board
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • create_signature_requestSend a PDF for electronic signature and get the signing links back.Reads text others writeCan send data out2 findings

    Why it is in this group

    • The name "create_signature_request" says "create": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.cc): what the tool writes goes there.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Info

      The description is 2,063 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ame thing is in its own API: /api/_esign (script /api/_esign/sign, TaskLiteSign)."

      What this check looks for
    Description, as the server wrote it
    Send a PDF for electronic signature and get the signing links back. One call: the PDF (an attachment already on an item, see list_uploaded_files / request_file_upload, or the bytes as base64), the signers, and optionally the row it belongs to. Each signer opens a personal link with an expiry, confirms a one-time code, reads the document and signs; the platform then seals the PDF with an evidence page and emails every signer the signed copy. With no fields, a signature page (name, signature, date per signer) is added at the end, so "read, then sign at the end" needs no coordinates. With itemId and signedFileColumnId (a file column on that item's board), the signed PDF is added to that cell when everyone has signed: build what happens next as an automation on "column value changed" of that column (set a status, notify, webhook). Delivery: by default the invitation and the code go to each signer's email. Per signer, channel="sms" or "whatsapp" (with a phone) sends them there instead; the invitation by WhatsApp only reaches a person who wrote to our number in the last day, and SMS reaches Israeli mobile numbers only. When the channel cannot be used, or the daily limit for SMS and WhatsApp is spent (per organization and per number, set by the platform), the platform falls back to email and records that in the audit trail. The one-time code never goes to the same channel as the link: with the link on SMS the code is tried on WhatsApp, with the link on WhatsApp on SMS, otherwise email. declinedValue must be an existing label for a status, dropdown or label column. If a signer declines, the document is stopped, the sender is emailed with the reason, and with declinedColumnId (a status, dropdown, label or text column on the item's board) the item gets declinedValue there (default text: declined), like the signed file does. sendEmail=false skips the invitation messages and the links are yours to hand over (open on the agent's phone). For a customer app the same thing is in its own API: /api/_esign (script /api/_esign/sign, TaskLiteSign).

    Annotations the server declares

    • title: Send a PDF for signature
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • google_calendar_busyWhen the user is already busy, across their own Google calendars (not the details, only the times), between two days: [{ date, from, to }] as wall clock in timeZone, so a booking p…Reads text others writeCan send data out2 findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Warn

      The server marks "google_calendar_busy" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    When the user is already busy, across their own Google calendars (not the details, only the times), between two days: [{ date, from, to }] as wall clock in timeZone, so a booking page can offer only free slots. Declined invitations, events marked free and holiday calendars do not count. Needs the busy-read consent: when it is missing the answer says so, and google_calendar_connect with includeBusyRead true makes the link for it.

    Annotations the server declares

    • title: Busy times in Google Calendar
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • google_calendar_create_eventAdd an event to a TaskLite calendar in the user's Google account.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "google_calendar_create_event" says "create": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Add an event to a TaskLite calendar in the user's Google account. Times are wall clock in timeZone; from and to both left out make an all-day event. key (e.g. the row id of the booking) makes it safe to call again: the same key updates the one event instead of adding a second, and brings it back if it was deleted. Returns the event with its id.

    Annotations the server declares

    • title: Add a calendar event
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • google_calendar_update_eventChange some fields of an event (id from google_calendar_list_events or create).Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "google_calendar_update_event" says "update": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Change some fields of an event (id from google_calendar_list_events or create). What is not given stays: moving only from/to keeps the day, moving only date keeps the hours (and the length of a multi-day event). attendees replaces the list; they are emailed only with sendInvitations true.

    Annotations the server declares

    • title: Change a calendar event
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • publish_appPublish an app, required before its API endpoints accept external calls.Can send data out1 finding

    Why it is in this group

    • The name "publish_app" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_app" says "publish": it sends or publishes something to other people.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Publish an app, required before its API endpoints accept external calls.

    Annotations the server declares

    • title: Publish app
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • run_telephony_syncSync now: read the call log from the PBX and write each new call as a row on the mapped board, as the signed-in user, through the board's normal path (so the board's automations ru…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "run_telephony_sync" says "run": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Sync now: read the call log from the PBX and write each new call as a row on the mapped board, as the signed-in user, through the board's normal path (so the board's automations run for every new row). Safe to repeat: a call already written is never written twice (deduped by the PBX call id), and a call the board refused is retried on the next run. With no range it reads from the saved position, otherwise from and to (local days, up to 31 days back) as a catch-up that leaves the position alone. At most 500 rows per run; run again for the rest. Look with preview_telephony_sync first. Needs a connected, mapped connection. Owner or admin of the app.

    Annotations the server declares

    • title: Sync calls to the board now
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • send_test_pushSend one real push notification to the given app users, to prove the chain works before an automation depends on it.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "send_test_push" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_test_push" says "send": it sends or publishes something to other people.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Send one real push notification to the given app users, to prove the chain works before an automation depends on it. Confirm with the user first: this reaches actual phones.

    Annotations the server declares

    • title: Send a test push
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 39Claude Code: ask
  • add_app_userGive a person access to an app by their phone number: the phone and a role, nothing else.Can send data out1 finding

    Why it is in this group

    • The name "add_app_user" says "add": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Give a person access to an app by their phone number: the phone and a role, nothing else. This is how the people who run an app (the business owner, a manager, staff) get into its admin screen, whose endpoints are in row-level security mode "shared". The person needs no invite code and does not have to sign in first. If the phone already signed in to this organization with a code, access is on at once and the answer has status "active" and their userId. Otherwise the answer has status "pending" and a pendingId: nothing is created for the number yet, and the access opens by itself the first time that phone signs in to the app with an SMS code (POST /auth/otp/send, then /auth/otp/verify). The phone is matched whatever its spelling: 054-1234567, +972 54 123 4567 and 972541234567 are one number; a number outside Israel needs its country code. Calling again for the same phone sets its role again, and switches back on a user who was switched off. Roles: editor (reads and writes), viewer (reads), submitter (creates). The app must still sign people in by phone code; a person who signs in another way (email and password, Google) is a different account, give them access with set_app_user_role after their first sign-in. Requires organization owner or admin (an editor gets 403).

    Annotations the server declares

    • title: Give a phone access to an app
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • add_commentPost a comment on an item's thread.Can send data outNo findings

    Why it is in this group

    • The name "add_comment" says "add": a word for a change.

    What it can reach

    • outboundThe name "add_comment" says "add" and "comment": it writes something other people read.
    Description, as the server wrote it
    Post a comment on an item's thread. To notify people, pass their user ids in mentionedUserIds (each also appears as an @mention). attachmentIds references already-uploaded files. Needs projectId and itemId.

    Annotations the server declares

    • title: Add a comment to an item
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • build_backendBuild a whole backend in one call from a spec you compose: the project, its boards, their typed columns (including relations between the boards), optional sample rows, and optional…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Build a whole backend in one call from a spec you compose: the project, its boards, their typed columns (including relations between the boards), optional sample rows, and optionally a published REST API with one endpoint per board and a server-side key. Use it whenever the user describes a system ("a backend for my repair shop: customers, orders, payments") instead of calling create_project, create_board, create_column, create_app, publish_app, create_app_endpoint and create_app_api_key one by one. You do the design, pick column types by meaning (phone, date, currency, dropdown/status with options for closed choices), link boards with a relation column (type "relation", relatedBoard: "<board name in this spec>", relationType: many_to_one for an order→customer link), and this tool executes it and returns one compact summary. API field names are derived from column names and never collide with reserved item fields, so there is nothing to retry. Boards are created as plain data tables (kind "data": only the columns you define, no task fields); set kind "tasks" on a board where people track work to do and want status, priority, assignee and due date built in. Every row still has a title. When the API has its own users, api.rowLevelSecurity: true gives every endpoint mode "owner"; a board may carry its own rowLevelSecurity instead (mode shared, phone or relation, with columns named as in this spec), e.g. Coaches { mode: "phone", phoneColumn: "Phone" } and Trainees { mode: "relation", relationColumn: "Coach", identityPhoneColumn: "Phone", allowInvites: true }.

    Annotations the server declares

    • title: Build a backend in one call
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • configure_app_settingsRead or change the settings object of an app.3 findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Info

      The description is 2,571 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...Other keys are stored as given and returned, and the server does not act on them."

      What this check looks for
    • Warn

      The server marks "configure_app_settings" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Read or change the settings object of an app. Call with only appId to read. To change, pass set: the keys in it are MERGED into the current settings (objects merge key by key at every depth, arrays and plain values replace, null removes a key). The server itself does not merge: PATCH replaces the whole settings object with what it is sent, so this tool reads the app, merges, and writes the full object back; two writers at the same moment can still overwrite each other, so do not run it in parallel on one app. Settings the server reads: ai (AI actions the app may run: { enabled: true, userDaily?, appDaily?, actions: { "<name>": { instructions, output?: "text"|"json", schema? (a JSON Schema, required for json), inputs?: { "<input>": { maxChars?, required? } }, tier?: "fast"|"smart", maxOutputTokens?, temperature?, audience?: "users"|"server", files?: { max? (1 to 5), required?, allowInstruction?, allowSchema? } } } }. The instructions stay on the server: a page runs an action by name with POST /apps/<slug>/api/_ai/v1/run { action, input } and the signed-in user's own token (the app's server may use a key with the "ai" scope). Every run is charged to the owner's usage allowance; 429 AI_QUOTA_EXCEEDED, AI_USER_DAILY_LIMIT or AI_RATE_LIMIT carry messageHe/message to show. An app without sign-in cannot run AI actions. With files set on an action (and the backend switch APP_AI_FILES on) the call may add files: [{ endpoint, itemId, field, attachmentId }] of a file column the caller can read through the app API, up to 10MB and 30 PDF pages each, and the model reads the PDF or image itself; allowInstruction lets the caller add an instruction string, allowSchema lets it send a JSON Schema for the answer; errors come back in Hebrew), passwordReset.returnUrls (array of up to 50 URLs the "reset password" email may send a user back to, matched by scheme, host, port and path prefix; needed only for a custom app scheme such as myapp://reset or a domain other than the app's own {slug}.tasklite.dev and its connected custom domains, which are always allowed; http is never accepted), language (the language of the password reset email: a value starting with "he" gives Hebrew, any other value English; left out, the user's own language decides), endUserDeletion.rows ("delete": when an end user deletes their account, the rows they wrote in this app are deleted with it and erased for good 30 days later; left out, the rows stay with the author shown as a deleted account). Other keys are stored as given and returned, and the server does not act on them.

    Annotations the server declares

    • title: Read or change app settings
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • configure_external_accessRead or change how EXTERNAL users (people who sign up to your app through TaskLite auth) get into an organization.3 findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Defaults to the credential organization"

      What this check looks for
    • Info

      The description is 2,114 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...l with no changes to just read the current settings. Requires organization admin."

      What this check looks for
    • Warn

      The server marks "configure_external_access" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Read or change how EXTERNAL users (people who sign up to your app through TaskLite auth) get into an organization. This policy governs sign-up by email and password and by Google. Sign-in by a phone code (POST /auth/otp/send, then /auth/otp/verify) obeys only "invite": under "closed", "approval" and "open" any phone that verifies a code becomes an external member of the organization, who reaches nothing until an endpoint's row-level security or the app's access list (add_app_user) gives them something; under "invite" a new phone needs an invite code or an add_app_user grant. The two ways in that obey the whole policy: email and password (POST /auth/register-external with this organizationId, then POST /auth/login), or Google (POST /auth/google-external with a Google ID token and this organizationId). Either way the answer carries a token the app sends as Authorization: Bearer on every App API call. registrationPolicy: "open", in at once; "approval", an organization admin approves each signup (TaskLite mails the admins on every signup, and the person once approved; unapproved users are never billed); "invite", a new person gets in only with an invite code (create_app_invite, or a code a user of the app minted on a relation endpoint with allowInvites): the app sends it as inviteCode with POST /auth/otp/verify, /auth/register-external or /auth/google-external, a sign-up without one is refused with 403 INVITE_REQUIRED and a bad code with 403 INVITE_INVALID, while people who are already members keep signing in as before; "closed" (the default), self-signup refused, external users are created by an admin. Under every policy a valid invite code admits its holder as if the organization were open, so "invite" is the policy for an app where people join only through someone who invited them (a coach inviting trainees). appLoginUrl: the page of YOUR app where these users log in, it becomes the "Log in" button in the approval email, so set it whenever you deploy an app that uses this flow; pass "" to clear. Call with no changes to just read the current settings. Requires organization admin.

    Annotations the server declares

    • title: Configure external user access
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • create_appCreate an app, a named API surface over the boards of a project, for an external frontend.1 finding

    Why it is in this group

    • The name "create_app" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Create an app, a named API surface over the boards of a project, for an external frontend. Then add endpoints and an API key.

    Annotations the server declares

    • title: Create app
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_app_api_keyCreate an API key for an app.1 finding

    Why it is in this group

    • The name "create_app_api_key" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Create an API key for an app. SECURITY: the key must live server-side only (env var, Next.js API routes), never in browser code. If the app has its own users, the server also sends `X-App-User: <user id>` with the key so per-user endpoints know who is acting.

    Annotations the server declares

    • title: Create app API key
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_app_endpointExpose a board as a REST endpoint of an app: /apps/{appSlug}/api/{slug}.1 finding

    Why it is in this group

    • The name "create_app_endpoint" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Expose a board as a REST endpoint of an app: /apps/{appSlug}/api/{slug}. exposedColumns limits which columns are readable/writable. rowLevelSecurity.enabled makes the endpoint per-user: the developer's server sends `X-App-User: <their user id>` next to the API key, and the endpoint returns, updates and deletes ONLY that user's rows (401 without the header). Use it whenever the app has its own users. rowLevelSecurity.mode chooses which rows a user reaches: owner (the rows they created), shared (all rows, for authorized users), phone (the rows that carry their verified phone) or relation (the rows linked through a relation column to the row that stands for them). An app with two kinds of people in one organization, coaches and their trainees, is built from these: the Coaches board in mode phone (phoneColumn = its phone column), so each coach reads and edits his own row; Trainees in mode relation with relationColumn = its Coach column and identityPhoneColumn = the Coaches phone column, so a coach who signed in by phone sees only his trainees; boards one hop further (weigh-ins of a trainee) in mode relation with relationColumn = the Trainee column and viaColumn = Trainees.Coach for the coach, plus a second endpoint on the same board without viaColumn for the trainee herself. A trainee becomes her row through an invite code (create_app_invite, or allowInvites so the coach mints it in the app) or link_app_user. In mode phone, rowLevelSecurity.phoneColumns adds more phone columns (up to 5 with phoneColumn): the row is reachable by a caller whose verified phone is in any of them, e.g. a second manager phone per row. Bodies of POST and PATCH may not write a phone column; only the owner sets them. The answer may carry `warnings`, e.g. an exposed formula column whose input columns are not exposed (add them, readOnly is fine, or its value comes back null).

    Annotations the server declares

    • title: Create app endpoint
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_app_inviteCreate an invite code for an app (8 characters shown as XXXX-XXXX, typed without regard to case or the dash).1 finding

    Why it is in this group

    • The name "create_app_invite" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Create an invite code for an app (8 characters shown as XXXX-XXXX, typed without regard to case or the dash). The person signs up or signs in through the app with the code: the app sends it as inviteCode with POST /auth/otp/verify, /auth/register-external or /auth/google-external, after it may check it with POST /auth/invites/check. An invite does one or both of two things, and must do at least one: itemId links the new user to that row, so they "are" the row for every endpoint in row-level security mode "relation" (invite a trainee to her own Trainees row, or a coach to his Coaches row); role puts them on the app's access list (viewer, editor or submitter), which is what mode "shared" endpoints check. A valid code also admits a new person into an organization whose registration policy is "invite" or "closed" (configure_external_access). An existing access row is never changed by an invite: it does not re-enable a user who was switched off and does not raise a role. Requires organization owner or admin (an editor gets 403). To let the app's own users invite (a coach invites his trainees from inside the app), set allowInvites on the relation endpoint instead; the app then calls POST /apps/{appSlug}/api/{endpointSlug}/{itemId}/invites.

    Annotations the server declares

    • title: Create invite code
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_automationCreate an automation on a board: when something happens, do something.Reads text others write1 finding

    Why it is in this group

    • The name "create_automation" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 5,837 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...l list_automations first so you do not add a second one that does the same thing."

      What this check looks for
    Description, as the server wrote it
    Create an automation on a board: when something happens, do something. The most useful action here is http_request, which calls an external API and writes the answer back into columns, pair it with the "scheduled" trigger and the board keeps itself up to date (prices, exchange rates, shipment status, weather). Triggers: item_created, item_deleted, status_changed, column_value_changed, date_approaching, scheduled. Actions: http_request, send_notification, send_email, send_push, change_status, set_column_value, create_cross_board_item, send_webhook, recompute_related_rollup. The scheduled trigger has no cron expression: the server checks once an hour, and triggerConfig takes { intervalHours, runAtHour } only (intervalHours: at least this many hours between runs, default 24; runAtHour: 0-23, run only during that hour of the day in UTC, not in the user's time zone, so convert: 08:00 in Israel is runAtHour 5 in summer and 6 in winter). A scheduled run executes the actions once for every row of the board that passes conditions, so filter with conditions. send_push sends a notification to the phones of app users through the app's own Firebase project (set up once per app: push_status; try it with send_test_push). Its config: { title, body, data, userIds, recipientsFromRelation, includeRowOwner, sound, badge, dataOnly }. title and body take {{column name}} placeholders, title defaults to the row title. Recipients are the union of: the row's owner under row-level security (includeRowOwner, default true; false leaves them out), userIds (fixed user ids, as in list_app_users), and recipientsFromRelation, a dotted path of column NAMES such as "Client.Coach.Coach user" that walks relation columns from this row and whose LAST segment must be a people column holding user ids (a single segment is a people column on this board); it does not resolve the user linked to a row by an invite or by phone, so without such a people column use userIds or the row owner. data is a flat object of strings the app reads to decide where to open (itemId and boardId are added). sound: "default" or the file name of a sound bundled in the app; badge: 0 to 99999, 0 clears; dataOnly: true shows nothing and delivers only data (no title, body, sound or badge; iOS may throttle or drop it). With no recipient the action is skipped, not failed. recompute_related_rollup keeps one column of a parent row equal to an aggregate of its child rows (a case's next action date from its open activities, an order total from its lines): put the automation on the CHILD board (triggers item_created, item_deleted and column_value_changed with no column named, which fires on any column change), config { relationColumnId (a relation column of the child board; targetRelation = its name works too), targetColumnId (a column of the parent board, which must be in the same project), aggregate: "min" | "max" | "count" | "sum", sourceColumnId (child column; not needed for count), where?: [{ field: "<child column id>", operator, value }] (AND, same operators as conditions, e.g. done not_equals "true"), whenEmpty?: number | null }. min and max take number, date or datetime columns and the target must be the same type; sum and count write to a number column. With no matching child the target is cleared (min, max) or set to 0 (count, sum) unless whenEmpty says otherwise. It writes through the normal path, so history and the parent board's own automations see the change, but it does not start another rollup. At most 5000 children per parent; more fails the run and writes nothing. Rows imported with board-import (new rows) and edits through the App API fire it; updating existing rows through board-import does not. Two more things every action list can use: a { type: "delay", config: { minutes | hours | days } } action pauses the run and resumes the actions after it later (reminders, follow-ups); and any network action (http_request, send_webhook, send_email, send_whatsapp) may carry config.retry: { attempts (1-5), delaySeconds (1-60) }. send_webhook accepts config.secret for an HMAC signature. send_email sends mail from the organization to the people on a row. Its config: { to, subject, body, columnEmailField, fromName, replyTo, kind, attachments }. kind is "transactional" (the default: orders, receipts, notifications) or "marketing" (promotional mail: it needs the Pro plan or higher and a verified sender domain, and it gets an unsubscribe footer; people who unsubscribed are skipped). attachments is an array of FILE column ids on the triggering row (or {{column.<id>}}): the stored files in those cells are attached, up to 5MB in total, and a missing file is skipped instead of failing the action. Email is counted per month by plan: Free 300, Plus 3000, Pro 20000 (read the numbers with get_email_usage); a message held back by the quota is recorded as skipped in the communications log and can be resent from there. To send email from an app's own server instead of an automation, POST /apps/<slug>/api/_email/send with the app server key (X-API-Key, never a user token; the key needs the "email" or "write" scope, see create_app_api_key): { to: [up to 50 addresses], subject, html or text, replyTo, kind, attachmentIds: [stored file ids] }; each app may send 500 a day (429 APP_EMAIL_DAILY_LIMIT). create_cross_board_item copies a new row to another board: config { targetBoardId, title?: "{{item.title}}", columnValues: { "<column id on the TARGET board>": "{{<column NAME on this board>}}" } }; there is no mapping field, and a column left out is not copied. To act only on some rows pass conditions, e.g. [{ field: "<column id on this board>", operator: "equals", value: "New seller" }]. Change an automation later with update_automation; call list_automations first so you do not add a second one that does the same thing.

    Annotations the server declares

    • title: Create automation
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_boardCreate a board (a data table) inside a project.No findings

    Why it is in this group

    • The name "create_board" says "create": a word for a change.
    Description, as the server wrote it
    Create a board (a data table) inside a project. Add typed columns with create_column afterwards. kind: "tasks" (default) also gives the board the built-in task columns, status, priority, assignee, due date, tags, for work people track; "data" creates a plain table with only the columns you add, for records such as customers, products or orders (requires a TaskLite server from 2026-09-06; older servers ignore kind).

    Annotations the server declares

    • title: Create board
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_columnAdd a typed column to a board.1 finding

    Why it is in this group

    • The name "create_column" says "create": a word for a change.

    Findings

    • Info

      The description is 2,736 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "..., otherwise it is null. Writes to formula, lookup and rollup columns are ignored."

      What this check looks for
    Description, as the server wrote it
    Add a typed column to a board. Valid types: text, rich_text, number, status, date, datetime, duration, people, checkbox, dropdown, label, priority, link, email, phone, relation, lookup, rollup, formula, rating, currency, file. Choose by meaning, date for dates, phone for phones, number/currency for amounts, dropdown/status (with settings.options as an array of labels) for closed choices; text is for free text only. An obvious name/type mismatch is rejected with the suggested type; pass force:true to override. Rules go in settings.validation: { unique, min, max, minLength, maxLength, pattern, patternMessage }, enforced on every write (UI, MCP, App API). Closed choices (dropdown/status) reject values outside settings.options unless settings.allowCustom is true. Sensitive identifiers (an Israeli ID number, a passport or account number) go in a sealed text column: settings.sealed: { normalize: "il_id" | "digits" | "text" }, usually with settings.validation.unique. The App API then stores only a keyed server-side fingerprint (hmac:v1:<hex>, under a secret key of the organization that never reaches the browser) and returns that on read; the page sends the plain value and must not hash it itself. A GET with filter[field]=<plain value> (eq, ne, in, empty) finds the row, a duplicate POST is refused with VALUE_NOT_UNIQUE, an invalid ID with INVALID_IL_ID. Every other write path (set_cell, create_item, the UI) refuses a plain value there (SEALED_COLUMN), and a column that already holds plain values cannot be sealed: create a new one. Formula column: settings.formula, e.g. { formula: "{Unit price} * {Qty}" }. Columns of the same row are written {Column Name} or {column-id} (a } inside a name is }; with two columns of one name use the id). Operators: + - * / %, brackets, comparison = != <> < <= >= , logic AND OR NOT; numbers, text in "double" or 'single' quotes, TRUE and FALSE (a true/false result is 1 / 0). Functions (not case sensitive): IF(cond, a, b), MIN, MAX, SUM, ROUND(x, digits), CEIL(x, step), FLOOR(x, step), ABS, COALESCE or IFBLANK, CONCAT, AND, OR, NOT. A blank cell counts as 0 in arithmetic; lookup and rollup columns can be read, and a lookup with several values must go through SUM, MIN, MAX or COALESCE. A formula that does not parse, names an unknown column or reads itself is refused with 400. Nothing is stored: the value is computed on the server each time the row is read ({ value, computed: true }, or error text in `error` when it cannot be computed). Through the App API a formula's value is returned only if every column it reads is exposed on the same endpoint (readOnly is fine) and visible to the caller, otherwise it is null. Writes to formula, lookup and rollup columns are ignored.

    Annotations the server declares

    • title: Add column
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_itemCreate an item (row) with all of its data in one call.No findings

    Why it is in this group

    • The name "create_item" says "create": a word for a change.
    Description, as the server wrote it
    Create an item (row) with all of its data in one call. cells maps columnId -> value (use get_board_schema for column ids); every cell is saved with the row. Use set_cell only for later edits.

    Annotations the server declares

    • title: Create item
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_projectCreate a project (a business process container).1 finding

    Why it is in this group

    • The name "create_project" says "create": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Create a project (a business process container). Boards with data live inside projects.

    Annotations the server declares

    • title: Create project
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • define_app_roleCreate a business role of an app's project, or change the label of an existing one (calling again with the same key and a label updates the label).1 finding

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Create a business role of an app's project, or change the label of an existing one (calling again with the same key and a label updates the label). A role is only a name; what it may do is written in the board policies. Example: key "manager", label "Agents manager". Roles can also come from the data itself with set_policy_identity (an employees board with a role column) instead of grant_app_role per person. Requires organization owner or admin.

    Annotations the server declares

    • title: Create or rename an app role
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • deploy_frontendDeploy a static frontend to TaskLite hosting and get a live URL https://{slug}.tasklite.dev (HTTPS, auto-published on first deploy, versions kept for rollback_deployment).Reads text others write1 finding

    Why it is in this group

    • The name "deploy_frontend" says "deploy": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Deploy a static frontend to TaskLite hosting and get a live URL https://{slug}.tasklite.dev (HTTPS, auto-published on first deploy, versions kept for rollback_deployment). Hand over the frontend in ONE of three ways: `files`, the files inline (path + content), the way to go from ChatGPT or any hosted client: write index.html and its assets, then deploy in the same turn; `zipUrl`, a public https URL of a zip (a Lovable/Bolt export, a GitHub release asset); `fromAppId`, a version already hosted in the same organization, copied on the server (start a new app from an existing site, or bring an old version back as a new one; get_deployment_files reads a version first). A real build that already exists on the person's machine fits none of these from a hosted server: tell them to drop the zip on the app's Versions screen (the adminUrl of the app, then Versions), which deploys the same way and keeps the same version history. In the frontend, call the app API via relative /api/{endpoint}, the hosting proxy injects the app identity, so no key ships to the browser. Link previews: WhatsApp, Facebook and Telegram do not run JS, so every client-side route shows the home page's title and image. A site can ship `_og-routes.json` next to index.html: { "routes": [ { "path": "/store/:slug", "endpoint": "sites", "match": "slug", "title": "name", "description": "about", "image": "logo" } ] }. path has literal segments and exactly one :param; endpoint is the slug of an App API endpoint of the same app that anonymous visitors can read; match is the alias of the column holding the param's value; title, description and image are column aliases (each optional; image must hold an http(s) URL). Only crawlers get the tags; people get the site as before.

    Annotations the server declares

    • title: Deploy frontend to TaskLite hosting
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • export_projectThe whole project as JSON, boards, columns with settings, items with their cells keyed by column id.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Defaults to the credential organization"

      What this check looks for
    Description, as the server wrote it
    The whole project as JSON, boards, columns with settings, items with their cells keyed by column id. For migrations, backups and reading a system back. Items are capped per board for the model's sake; the REST endpoint GET /organizations/{orgId}/projects/{projectId}/export.json returns everything.

    Annotations the server declares

    • title: Export project as JSON
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • google_calendar_connectGet the link that connects the signed-in user's Google Calendar to TaskLite.Reads private data2 findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "google_calendar_connect" says "calendar": it reads calendars.
    • private-dataThe description's first sentence says "get" and "calendar": it reads calendars.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Warn

      The server marks "google_calendar_connect" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Get the link that connects the signed-in user's Google Calendar to TaskLite. Send connectUrl to the person as is: they open it, approve on Google's own page, and come back. It lasts 24 hours and can be opened again in that time; calling again makes a new one. Only that person can approve: the link connects whichever Google account approves it to THIS TaskLite user, so send it only to them. With appId the browser comes back to that app's site, on the domain the app has at that moment (its custom domain, else <slug>.tasklite.dev), at returnPath (a path such as "/#admin"), or at the path saved with google_calendar_set_return_path, else "/". Without appId it ends on a TaskLite page that says the calendar is connected. includeBusyRead true also asks to read busy time (the person's existing meetings) so bookings can avoid them; Google calls that a sensitive permission and shows a stronger consent screen, so ask for it only when the person wants it. Asking again later keeps the write access already given. Afterwards google_calendar_status shows connected.

    Annotations the server declares

    • title: Get a Google Calendar connection link
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • google_calendar_ensure_calendarFind, or create the first time, the calendar TaskLite keeps in the user's Google account under a name (default "פגישות").Reads private dataReads text others write2 findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "google_calendar_ensure_calendar" says "calendar": it reads calendars.
    • private-dataThe description's first sentence says "find" and "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Warn

      The server marks "google_calendar_ensure_calendar" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Find, or create the first time, the calendar TaskLite keeps in the user's Google account under a name (default "פגישות"). It appears in their Google Calendar beside their own calendars, with its own colour, on every device. Returns { calendarId, created }. The event tools find it by name themselves; call this to know the id or to create it ahead.

    Annotations the server declares

    • title: Find or create the app's calendar
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • google_calendar_set_return_pathSave on an app the page the browser returns to after a Google Calendar connection started for that app (google_calendar_connect with appId, or the site's own "connect" button throu…1 finding

    Why it is in this group

    • The name "google_calendar_set_return_path" says "set": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Save on an app the page the browser returns to after a Google Calendar connection started for that app (google_calendar_connect with appId, or the site's own "connect" button through POST /integrations/oauth/google_calendar/initiate with appId). Only a path, e.g. "/#admin": the domain is always the app's own at the moment of connecting, so a later domain change needs nothing here. Stored as settings.googleCalendar.returnPath. null removes it (back to "/").

    Annotations the server declares

    • title: Set where the Google connection returns to
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • grant_app_roleGive an app user a business role (a user can hold several).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Give an app user a business role (a user can hold several). Takes the userId from list_app_users and a role key from list_app_roles. expiresAt makes the grant temporary. Granting the same pair again changes only expiresAt. This is for personal exceptions; for a whole team prefer set_policy_identity, which reads the roles from an employees board. Requires organization owner or admin.

    Annotations the server declares

    • title: Give a user an app role
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • push_statusWhether an app can send push notifications to phones, and how many devices are registered.2 findings

    Why it is in this group

    • The name "push_status" says "push": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Warn

      The server marks "push_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "push_status" says "push": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Whether an app can send push notifications to phones, and how many devices are registered. Push goes out through the customer's OWN Firebase project, so it has to be configured once per app before send_push automations do anything. This tool never returns the key.

    Annotations the server declares

    • title: Push status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • reorder_columnsSet the display order of a board's columns.No findings

    Why it is in this group

    • The description's first verb is "set": a word for a change.
    Description, as the server wrote it
    Set the display order of a board's columns. Pass every column id in the wanted order (get_board_schema lists them).

    Annotations the server declares

    • title: Reorder columns
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • request_file_uploadCreate a link that puts files onto an item from outside TaskLite: the customer's photos, a signed contract, a logo, a build zip.Reads text others write1 finding

    Why it is in this group

    • The name "request_file_upload" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Create a link that puts files onto an item from outside TaskLite: the customer's photos, a signed contract, a logo, a build zip. Returns an address like https://app.tasklite.net/upload/<token> that anyone you hand it to can use with no account, no login and no API key; pass clientEmail and TaskLite emails the link for you. What arrives lands as attachments on that item, and list_uploaded_files reads them back with a download URL. This is the answer when the person has the file and the model does not: a hosted client cannot read a folder on someone's machine. The link is public for as long as it lasts, so keep expiryDays short and maxFiles tight, and revoke_upload_link when the material is in.

    Annotations the server declares

    • title: Create a file upload link
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • rollback_deploymentPoint the live URL back at a previous deployment version (see list_deployments for available versions).Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Point the live URL back at a previous deployment version (see list_deployments for available versions).

    Annotations the server declares

    • title: Roll back a frontend deployment
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • set_cellSet a single cell value on an item by columnId.No findings

    Why it is in this group

    • The name "set_cell" says "set": a word for a change.
    Description, as the server wrote it
    Set a single cell value on an item by columnId.

    Annotations the server declares

    • title: Set cell value
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • set_cells_if_unchangedCompare-and-set on cells of one item, all or none.3 findings

    Why it is in this group

    • The name "set_cells_if_unchanged" says "set": a word for a change.

    Findings

    • Warn

      The input schema at properties.cells.items.properties.expected.anyOf[0].$ref contains a 48-character base64 string.

      Matched text

      inputSchema.properties.cells.items.properties.expected.anyOf[0].$ref: "#/properties/cells/items/properties/value/anyOf/0"

      What this check looks for
    • Warn

      The input schema at properties.cells.items.properties.expected.anyOf[1].$ref contains a 48-character base64 string.

      Matched text

      inputSchema.properties.cells.items.properties.expected.anyOf[1].$ref: "#/properties/cells/items/properties/value/anyOf/1"

      What this check looks for
    • Warn

      The input schema at properties.cells.items.properties.expected.anyOf[2].$ref contains a 48-character base64 string.

      Matched text

      inputSchema.properties.cells.items.properties.expected.anyOf[2].$ref: "#/properties/cells/items/properties/value/anyOf/2"

      What this check looks for
    Description, as the server wrote it
    Compare-and-set on cells of one item, all or none. Each cell carries the value you read (`expected`, null = empty) and the value to write. If any cell no longer holds its `expected`, nothing is written and the answer is an error with code CELL_CONFLICT and `conflicts` [{columnId, current}]: read again (use `current`), decide again, and never resend the same call. CELL_BUSY (the row is being written) also writes nothing: read again, then retry. Plain columns only (not relation, file, lookup, rollup, formula, button or system columns). Use set_cell for a write that needs no precondition.

    Annotations the server declares

    • title: Set cells if unchanged
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • set_policy_identityDerive "who is this user and what is their role" from the data, instead of a grant per person: point at the employees board, its phone/email column, the column that says what each …1 finding

    Why it is in this group

    • The name "set_policy_identity" says "set": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Derive "who is this user and what is their role" from the data, instead of a grant per person: point at the employees board, its phone/email column, the column that says what each person does, and a map from that column's values to role keys. A signed-in user whose verified phone (or email) is in a row of that board gets that row's roles; a row that is not active gives none. Full replace. Example: { "board": "<Employees board id>", "phoneColumn": "<Phone column id>", "roleColumn": "<Position column id>", "roleMap": { "Agent": ["agent"], "Agents manager": ["manager"], "Owner": ["owner"] }, "activeColumn": "<Status column id>", "activeValues": ["Active"] }. Board and columns are ids (get_board_schema). A grant (grant_app_role) adds to what the board gives. Requires organization owner or admin.

    Annotations the server declares

    • title: Derive roles from an employees board
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • simulate_requestDry-run one app API request in the name of a user and get the verdict (allowed or refused, and why), changing nothing: the endpoint slug, the HTTP method (or the name of a policy a…Can send data out2 findings

    Why it is in this group

    • The name "simulate_request" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    • Warn

      The server marks "simulate_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "simulate_request" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Dry-run one app API request in the name of a user and get the verdict (allowed or refused, and why), changing nothing: the endpoint slug, the HTTP method (or the name of a policy action, with its itemId) and optionally the column keys the body would carry. Use it to prove that a forbidden thing is refused (an agent PATCHing assignedTo, reading another agent's row) and an allowed one passes. Requires organization owner or admin.

    Annotations the server declares

    • title: Dry-run an app request for a user
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • start_telephony_connectionStart connecting an app to a phone system (PBX) and get the one-time link the CUSTOMER opens to type the API token themselves.1 finding

    Why it is in this group

    • The name "start_telephony_connection" says "start": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Start connecting an app to a phone system (PBX) and get the one-time link the CUSTOMER opens to type the API token themselves. The token never passes through the chat, you or the logs: do not ask for it, do not accept it pasted. Send the link to the customer as is. It works once, for 24 hours, and is spent only after the token passes a check against the PBX (a typo can be fixed on the same page). Calling again makes a new link and replaces the unused one; the stored token is kept until a new one is typed. Pick the provider from list_telephony_providers. For paycall pass publicConfig.baseUrl, the server address of that customer's tenant, e.g. https://master.ippbx.co.il/ippbx_api/v1.4/api/info (https only, must end with /api/info). Owner or admin of the app. Afterwards: get_telephony_connection shows connected, test_telephony_connection proves it, configure_telephony_mapping says where calls go.

    Annotations the server declares

    • title: Start a phone system connection
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • test_telephony_connectionCheck the stored token against the customer's phone system: a one-day call log read.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Check the stored token against the customer's phone system: a one-day call log read. Answers { ok, message } with a Hebrew message that can be shown to the customer as is, and records the result on the connection. It only reads from the PBX. Owner or admin of the app.

    Annotations the server declares

    • title: Test a phone system connection
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • update_app_endpointChange an existing endpoint, most often to set exposedColumns on one that was created without them.1 finding

    Why it is in this group

    • The name "update_app_endpoint" says "update": a word for a change.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Change an existing endpoint, most often to set exposedColumns on one that was created without them. Get the endpoint id from list_app_endpoints and the column ids from get_board_schema. In rowLevelSecurity mode phone, phoneColumns adds more phone columns next to phoneColumn (up to 5 in all; a caller whose verified phone is in any of them reaches the row); send it again with every other field, since the object replaces the stored one. The answer may carry `warnings`, e.g. an exposed formula column whose input columns are not exposed (add them, readOnly is fine, or its value comes back null).

    Annotations the server declares

    • title: Update app endpoint
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_automationChange an existing automation: its actions, conditions, trigger config or name, or switch it off with isActive false.No findings

    Why it is in this group

    • The name "update_automation" says "update": a word for a change.
    Description, as the server wrote it
    Change an existing automation: its actions, conditions, trigger config or name, or switch it off with isActive false. Fields left out stay as they are; actions and conditions, when given, replace the whole list. Use it to fix an automation instead of creating a second one next to it. Get the id from list_automations. For send_email actions, config.kind is transactional (default) or marketing (Pro plan or higher, verified sender domain, unsubscribe footer) and config.attachments is an array of file column ids on the row; see create_automation.

    Annotations the server declares

    • title: Update automation
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_boardRename a board or change its description.No findings

    Why it is in this group

    • The name "update_board" says "update": a word for a change.
    Description, as the server wrote it
    Rename a board or change its description. Structure (columns) is changed with update_column / delete_column / reorder_columns.

    Annotations the server declares

    • title: Update board
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_columnChange a column after the fact: rename it, change its type (e.g.No findings

    Why it is in this group

    • The name "update_column" says "update": a word for a change.
    Description, as the server wrote it
    Change a column after the fact: rename it, change its type (e.g. number -> currency), replace settings (dropdown options), or set isRequired / isHidden. A type change converts existing values (number↔currency, text→number/date/checkbox, anything→text) and clears the ones that cannot convert; the response carries conversion: { converted, cleared }. settings.validation rules apply here too.

    Annotations the server declares

    • title: Update column
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_commentEdit the text of an existing comment.Can send data outNo findings

    Why it is in this group

    • The name "update_comment" says "update": a word for a change.

    What it can reach

    • outboundThe name "update_comment" says "update" and "comment": it writes something other people read.
    Description, as the server wrote it
    Edit the text of an existing comment. Only the author can edit their comment. Needs projectId, itemId and the commentId.

    Annotations the server declares

    • title: Edit a comment
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_itemUpdate item fields (title, description, status, priority, dueDate, tags).No findings

    Why it is in this group

    • The name "update_item" says "update": a word for a change.
    Description, as the server wrote it
    Update item fields (title, description, status, priority, dueDate, tags). On a data board the task fields (status, priority, dueDate, tags) are hidden: its columns, status included, are set with set_cell.

    Annotations the server declares

    • title: Update item
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 35Show 35 read-only tools
  • explain_accessSay what a user, or a list of roles, may do on a board under its policy: which rows they read and write, which columns, create and delete.1 finding

    Why it is in this group

    • The name "explain_access" says "explain": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Say what a user, or a list of roles, may do on a board under its policy: which rows they read and write, which columns, create and delete. Pass boardId and exactly one of userId (an app user from list_app_users; the answer includes the roles that person has) or roles (role keys, to try a role before anyone holds it). Changes nothing; use it after every set_board_policy. Requires organization owner or admin.

    Annotations the server declares

    • title: Explain what a user or roles may do on a board
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • fetchOne project, board or item in full, by the id search returned (project:<id>, board:<projectId>:<boardId>, item:<projectId>:<boardId>:<itemId>) or by an app URL path.Reads text others write1 finding

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Only needed for project ids when the credential has no default organization; otherwise..."

      What this check looks for
    Description, as the server wrote it
    One project, board or item in full, by the id search returned (project:<id>, board:<projectId>:<boardId>, item:<projectId>:<boardId>:<itemId>) or by an app URL path. Returns { id, title, text, url, metadata }, the ChatGPT fetch contract; text is the record as JSON.

    Annotations the server declares

    • title: Fetch one record by id
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_app_specGet the machine-readable spec of an app: base URL, endpoints, methods, fields, auth.Reads text others write1 finding

    Why it is in this group

    • The name "get_app_spec" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Get the machine-readable spec of an app: base URL, endpoints, methods, fields, auth. Two formats: "tasklite" (default), the compact shape the frontend prompts are built from, and "openapi", a standard OpenAPI 3.1 document for developers and other tools. When the user asks for the OpenAPI spec, or wants to hand the API to a developer, pass format "openapi". appId accepts either the app UUID or its slug (app-xxxxxx); list_apps shows both. The returned baseUrl is absolute, use it verbatim, do not rebuild it from the admin URL.

    Annotations the server declares

    • title: Get app spec
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_board_policyRead a board's access policy: { boardId, policy, updatedAt, updatedBy }, policy null when the board has none.1 finding

    Why it is in this group

    • The name "get_board_policy" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Read a board's access policy: { boardId, policy, updatedAt, updatedBy }, policy null when the board has none. A policy only takes effect on endpoints whose rowLevelSecurity mode is "policy". Requires organization owner or admin.

    Annotations the server declares

    • title: Read a board's access policy
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_board_schemaGet a board with its full column schema (ids, names, types, settings).No findings

    Why it is in this group

    • The name "get_board_schema" says "get": a word for reading.
    Description, as the server wrote it
    Get a board with its full column schema (ids, names, types, settings). Call this before creating items with cells.

    Annotations the server declares

    • title: Read board schema
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_cellsRead cells of one item from the database (not a cache): one current value per column, the value set_cells_if_unchanged compares.Reads private dataNo findings

    Why it is in this group

    • The name "get_cells" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "database": it reads databases.
    Description, as the server wrote it
    Read cells of one item from the database (not a cache): one current value per column, the value set_cells_if_unchanged compares. Use it to decide a conditional write, and pass each value back as `expected` exactly as it came.

    Annotations the server declares

    • title: Get cells
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_deployment_filesRead back what a hosted frontend version is made of: every file with its size and its URL on that version, and the full text of the text files (HTML, CSS, JS, JSON, SVG...).Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_deployment_files" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_deployment_files" says "get" and "file": it reads files.
    • private-dataThe description's first sentence says "read" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Read back what a hosted frontend version is made of: every file with its size and its URL on that version, and the full text of the text files (HTML, CSS, JS, JSON, SVG...). This is how a new conversation continues a site an earlier one built: "take my Krispool site and keep going" starts here, not from scratch. For a site written by hand the files ARE the source. For a bundled build (Vite, React) the JS is minified output: fine to inspect, not something to edit, so ask for the project's source instead. Images and other binaries come back as URLs only. Text is capped at 512KB per file and 4MB per call; narrow with `paths` for a big site. To start another app from this version, or bring an old version back as a new one, use deploy_frontend with fromAppId.

    Annotations the server declares

    • title: Read a deployed version's files
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_email_usageHow much of the monthly email quota an organization has used: emails sent this month, emails waiting in the queue, the plan limit (Free 300, Plus 3000, Pro 20000; null means unlimi…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_email_usage" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_email_usage" says "get" and "email": it reads mail.
    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe name "get_email_usage" says "get" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Defaults to the credential organization"

      What this check looks for
    Description, as the server wrote it
    How much of the monthly email quota an organization has used: emails sent this month, emails waiting in the queue, the plan limit (Free 300, Plus 3000, Pro 20000; null means unlimited), whether the plan allows marketing email, and whether sending is paused for the organization (too many bounces or complaints). Covers email sent by automations, the communications endpoints and app servers (POST /apps/<slug>/api/_email/send).

    Annotations the server declares

    • title: Get email usage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_frontend_promptGet a ready-made prompt describing the app backend, for pasting into a frontend generator (v0/bolt/lovable/cursor).1 finding

    Why it is in this group

    • The name "get_frontend_prompt" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Get a ready-made prompt describing the app backend, for pasting into a frontend generator (v0/bolt/lovable/cursor). appId accepts the app UUID or its slug (app-xxxxxx), use list_apps to find it.

    Annotations the server declares

    • title: Get frontend prompt
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_item_historyRead the change history of one item (row), newest first: who changed which field, from what to what, when, through which channel, with the event and reason when a named action made…1 finding

    Why it is in this group

    • The name "get_item_history" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Read the change history of one item (row), newest first: who changed which field, from what to what, when, through which channel, with the event and reason when a named action made the change. Returns { items: [{ field, fieldId, from, to, at, actor: { userId, name }, channel, event, reason }], nextBefore }. Page backwards by passing nextBefore as `before`. Needs access to the item's board.

    Annotations the server declares

    • title: Read the change history of an item
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_permission_historyWhat changed in who may do what in an app, newest first: role defined, renamed or deleted (with who lost it), a role granted or revoked, the identity board set or cleared, a board …1 finding

    Why it is in this group

    • The name "get_permission_history" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    What changed in who may do what in an app, newest first: role defined, renamed or deleted (with who lost it), a role granted or revoked, the identity board set or cleared, a board policy set or deleted. Each change has when (at), who made it (by), the role, board or user it is about, and the value before and after. The server keeps it 180 days. A role that comes from the people board (set_policy_identity) changes by editing that row, and that change is in the row's history (get_item_history), not here. Requires organization owner or admin.

    Annotations the server declares

    • title: Read the history of permission changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_policy_identityRead the project's role identity: which board holds the people and how their rows map to roles (see set_policy_identity).1 finding

    Why it is in this group

    • The name "get_policy_identity" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Read the project's role identity: which board holds the people and how their rows map to roles (see set_policy_identity). Returns { identity }, null when none is set. Requires organization owner or admin.

    Annotations the server declares

    • title: Read where roles come from in the data
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_signature_requestOne document sent for signature: status, signers and their state, and when complete a short-lived download URL of the signed PDF (with its evidence page).Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_signature_request" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    One document sent for signature: status, signers and their state, and when complete a short-lived download URL of the signed PDF (with its evidence page).

    Annotations the server declares

    • title: Read a signature request
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_telephony_connectionRead-only.1 finding

    Why it is in this group

    • The name "get_telephony_connection" says "get": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Read-only. The phone system connection of an app: provider, status (pending = link made and no token typed yet, connected, error), the public settings, whether a token is stored (never the token), the board mapping, the last sync result and the last error. connection is null when nothing was started.

    Annotations the server declares

    • title: Read an app's phone system connection
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • google_calendar_list_eventsThe events of a TaskLite calendar in the user's Google account that touch the days from..to (inclusive), in order, with times as the wall clock in timeZone.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "google_calendar_list_events" says "list": a word for reading.

    What it can reach

    • private-dataThe name "google_calendar_list_events" says "list" and "calendar": it reads calendars.
    • private-dataThe description's first sentence says "calendar": it reads calendars.
    • private-dataThe input names a calendar (input.calendarId), and the tool reads: it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    The events of a TaskLite calendar in the user's Google account that touch the days from..to (inclusive), in order, with times as the wall clock in timeZone. Each: id (for update and delete), summary, description, location, date, endDate, from, to (null for an all-day event), allDay, attendees, htmlLink.

    Annotations the server declares

    • title: List calendar events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • google_calendar_statusWhether the signed-in user has connected Google Calendar to TaskLite, which Google account, and what the connection may do: canWriteOwnCalendars (add, change and delete events in t…Reads private data1 finding

    Why it is in this group

    • The name "google_calendar_status" says "status": a word for reading.

    What it can reach

    • private-dataThe name "google_calendar_status" says "status" and "calendar": it reads calendars.
    • private-dataThe description's first sentence says "calendar": it reads calendars.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Whether the signed-in user has connected Google Calendar to TaskLite, which Google account, and what the connection may do: canWriteOwnCalendars (add, change and delete events in the calendars TaskLite creates in that account), canReadBusy (read when the person is already busy in their other calendars, a second consent), needsReconnect (Google stopped accepting it: a new google_calendar_connect link is needed). The connection belongs to the user, not to an app: every app of the user writes through it. Never returns a token.

    Annotations the server declares

    • title: Google Calendar connection status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_app_endpointsList an app's REST endpoints, slug, board, allowed methods, and how many columns each exposes.1 finding

    Why it is in this group

    • The name "list_app_endpoints" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    List an app's REST endpoints, slug, board, allowed methods, and how many columns each exposes. An endpoint exposing 0 columns is broken: it returns only item metadata and silently discards writes.

    Annotations the server declares

    • title: List app endpoints
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_app_invitesList the invite codes of an app, newest first (the latest 200): the ones created with create_app_invite and the ones the app's own users minted through a relation endpoint with all…1 finding

    Why it is in this group

    • The name "list_app_invites" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    List the invite codes of an app, newest first (the latest 200): the ones created with create_app_invite and the ones the app's own users minted through a relation endpoint with allowInvites (createdVia admin or app). Each carries id, code, itemId, role, label, maxUses, useCount, expiresAt, revokedAt and status: active, used (no uses left), expired or revoked.

    Annotations the server declares

    • title: List invite codes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_app_role_grantsList the role grants of an app's project, as { grants }: who holds which role and until when.1 finding

    Why it is in this group

    • The name "list_app_role_grants" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    List the role grants of an app's project, as { grants }: who holds which role and until when. Pass userId to see one person's. Roles that come from the employees board (set_policy_identity) are not grants and are not listed here; explain_access with a userId shows the roles a person ends up with. Requires organization owner or admin.

    Annotations the server declares

    • title: List who holds which app role
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_app_rolesList the business roles of an app's project, as { roles: [{ key, label }] }.1 finding

    Why it is in this group

    • The name "list_app_roles" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    List the business roles of an app's project, as { roles: [{ key, label }] }. Roles are what board policies (set_board_policy) name in their `roles` lists; they are separate from the app access role (viewer, editor, submitter) of add_app_user. Requires organization owner or admin.

    Annotations the server declares

    • title: List an app's roles
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_app_usersList the people of an app, as { users, pending }.1 finding

    Why it is in this group

    • The name "list_app_users" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    List the people of an app, as { users, pending }. users: everyone who ever called it with X-App-User or signed in to it with a code. Each has userId (the id set_app_user_role, remove_app_user, link_app_user, list_app_user_links and send_test_push take), externalId (the developer's own id for them, or null for a user who signed in by code), name, phone (the phone they proved with a code, or null), source (api or otp), role (viewer, editor or submitter), isActive, hasAccessRow, lastSeenAt and itemCount (rows they own on the app's boards). hasAccessRow says whether they are on the app's access list: when it is false, role and isActive are only defaults, and an endpoint in row-level security mode "shared" refuses them with 403 until add_app_user or set_app_user_role puts them on the list. pending: the phones add_app_user is still holding access for, each with id, phone, role, createdAt, expiresAt and status (pending, or expired); they get in on their first sign-in with a code. Use it to see who can use the app and to find the userId of a person.

    Annotations the server declares

    • title: List app users
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_appsList the apps in the organization, id, slug, status.1 finding

    Why it is in this group

    • The name "list_apps" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    List the apps in the organization, id, slug, status. Call this first when you need an app id: the slug (app-xxxxxx) is what shows up in URLs and in generated code, and this is how you map it back to the app.

    Annotations the server declares

    • title: List apps
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_automationsList the automations on a board, so you can see what already runs before adding another.No findings

    Why it is in this group

    • The name "list_automations" says "list": a word for reading.
    Description, as the server wrote it
    List the automations on a board, so you can see what already runs before adding another.

    Annotations the server declares

    • title: List automations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_boardsList the boards inside a project, id, name, description.No findings

    Why it is in this group

    • The name "list_boards" says "list": a word for reading.
    Description, as the server wrote it
    List the boards inside a project, id, name, description. Every other board tool needs a boardId, and this is the only way to discover one without being handed a URL.

    Annotations the server declares

    • title: List boards
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_commentsList the comments (the correspondence thread) on an item, oldest first.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_comments" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "thread": it reads messages.
    • untrusted-inputThe name "list_comments" says "list" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    List the comments (the correspondence thread) on an item, oldest first. Each comment includes its author and any @mentions. Needs projectId and itemId (get itemId from query_items).

    Annotations the server declares

    • title: List item comments
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_deploymentsList the hosted-frontend deployments of an app, versions, which one is live, and the public URL.Reads text others write1 finding

    Why it is in this group

    • The name "list_deployments" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    List the hosted-frontend deployments of an app, versions, which one is live, and the public URL.

    Annotations the server declares

    • title: List frontend deployments
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_organizationsList the organizations the authenticated user belongs to.No findings

    Why it is in this group

    • The name "list_organizations" says "list": a word for reading.
    Description, as the server wrote it
    List the organizations the authenticated user belongs to. Use the returned id as organizationId in other tools.

    Annotations the server declares

    • title: List organizations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_projectsList projects in an organization.1 finding

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Defaults to the credential organization"

      What this check looks for
    Description, as the server wrote it
    List projects in an organization. The API returns 50 per page, an organization with more than that needs page 2 and beyond, so check the returned total before assuming a project does not exist.

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_signature_requestsDocuments sent for signature, newest first, with each signer's state (sent, viewed, signed, declined).Reads private data1 finding

    Why it is in this group

    • The name "list_signature_requests" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Documents sent for signature, newest first, with each signer's state (sent, viewed, signed, declined). Filter by the row they belong to or by status (out_for_signature, completed, declined, voided, expired, failed).

    Annotations the server declares

    • title: List documents sent for signature
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_telephony_providersRead-only.No findings

    Why it is in this group

    • The name "list_telephony_providers" says "list": a word for reading.
    Description, as the server wrote it
    Read-only. List the phone systems (PBX providers) an app can be connected to, what each can do (call log, live calls, recordings, click-to-call), and which fields it needs: public settings such as the server address go to start_telephony_connection, secret fields (the API token) are typed by the customer on a one-time page and never pass through you.

    Annotations the server declares

    • title: List phone system providers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_uploaded_filesThe files attached to an item, including everything that came in through a request_file_upload link, each with a download URL that is signed and short lived (mint a fresh one by ca…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "list_uploaded_files" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_uploaded_files" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    The files attached to an item, including everything that came in through a request_file_upload link, each with a download URL that is signed and short lived (mint a fresh one by calling again). Also lists the upload links on the item and how many files each has taken, which is how to tell whether the person you asked has delivered.

    Annotations the server declares

    • title: List files on an item
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preview_telephony_syncRead-only for TaskLite: reads the call log from the customer's PBX for a range and shows what a sync would write, without writing anything or moving the sync position.Reads text others write1 finding

    Why it is in this group

    • The name "preview_telephony_sync" says "preview": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.organizationId.description mentions "credential".

      Matched text

      inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

      What this check looks for
    Description, as the server wrote it
    Read-only for TaskLite: reads the call log from the customer's PBX for a range and shows what a sync would write, without writing anything or moving the sync position. Returns counts (fetched, already on the board) and the last 20 calls as board rows (title, cells by column id, the customer and employee matched). Works before a mapping exists (then rows come back unmapped), so use it to look at the real calls first. from and to are local days (YYYY-MM-DD), up to 31 days back; omit both for the same window a scheduled sync would read. Owner or admin of the app.

    Annotations the server declares

    • title: Preview a call log sync
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • query_itemsList items (rows) of a board, including their cell values.No findings

    Why it is in this group

    • The name "query_items" says "query": a word for reading.
    Description, as the server wrote it
    List items (rows) of a board, including their cell values. Returns all items unless limit/page are given (the API defaults to 50 per page when unpaged, so the tool pages through and concatenates). Narrow the result with search, status, priority and sort instead of fetching everything. This is the admin view; the REST endpoints of a published app take a fuller grammar, filter[column][gte], relation filters, per-field search, see get_app_spec.

    Annotations the server declares

    • title: List items
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

3575 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 11 private-data tools breaks every one.

deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__tasklite__get_cells",
      "mcp__tasklite__get_deployment_files",
      "mcp__tasklite__get_email_usage",
      "mcp__tasklite__get_signature_request",
      "mcp__tasklite__google_calendar_connect",
      "mcp__tasklite__google_calendar_ensure_calendar",
      "mcp__tasklite__google_calendar_list_events",
      "mcp__tasklite__google_calendar_status",
      "mcp__tasklite__list_comments",
      "mcp__tasklite__list_signature_requests",
      "mcp__tasklite__list_uploaded_files"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
67
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.tasklite.net/.well-known/oauth-protected-resource
Authorization servers
https://api.tasklite.net
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 67 tools that change things (19 destructive, 9 irreversible, 39 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.tasklite.net/mcp: tools/list returned 102 tools to an anonymous client, including delete_board (destructive), delete_project (destructive), delete_column (destructive), delete_item (destructive), delete_comment (destructive) and 62 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 54 to 67
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 51 to 54

Findings

Matches of fixed checks, with the text they matched.

11 warn80 info
  • The server marks "configure_external_access" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The input schema at properties.cells.items.properties.expected.anyOf[0].$ref contains a 48-character base64 string.

    Matched text

    inputSchema.properties.cells.items.properties.expected.anyOf[0].$ref: "#/properties/cells/items/properties/value/anyOf/0"

    What this check looks for
  • The input schema at properties.cells.items.properties.expected.anyOf[1].$ref contains a 48-character base64 string.

    Matched text

    inputSchema.properties.cells.items.properties.expected.anyOf[1].$ref: "#/properties/cells/items/properties/value/anyOf/1"

    What this check looks for
  • The input schema at properties.cells.items.properties.expected.anyOf[2].$ref contains a 48-character base64 string.

    Matched text

    inputSchema.properties.cells.items.properties.expected.anyOf[2].$ref: "#/properties/cells/items/properties/value/anyOf/2"

    What this check looks for
  • The server marks "push_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "push_status" says "push": a word for a change.

    What this check looks for
  • The server marks "google_calendar_connect" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "get": a word for reading.

    What this check looks for
Show 85 more findings
  • The server marks "google_calendar_ensure_calendar" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "find": a word for reading.

    What this check looks for
  • The server marks "google_calendar_busy" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "configure_app_settings" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The server marks "check_invite_code" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_invite_code" says "invite": a word for sending, and what is sent cannot be taken back.

    What this check looks for
  • The server marks "simulate_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "simulate_request" says "request": a word for a change.

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Defaults to the credential organization"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Defaults to the credential organization"

    What this check looks for
  • The description is 2,114 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...l with no changes to just read the current settings. Requires organization admin."

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Defaults to the credential organization"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The description is 2,736 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "..., otherwise it is null. Writes to formula, lookup and rollup columns are ignored."

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Defaults to the credential organization"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The description is 2,063 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ame thing is in its own API: /api/_esign (script /api/_esign/sign, TaskLiteSign)."

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The description is 2,571 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...Other keys are stored as given and returned, and the server does not act on them."

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The description is 6,324 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...request before telling the user it is done. Requires organization owner or admin."

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The description is 5,837 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...l list_automations first so you do not add a second one that does the same thing."

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • Infofetch

    The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Only needed for project ids when the credential has no default organization; otherwise..."

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for
  • The input schema at properties.organizationId.description mentions "credential".

    Matched text

    inputSchema.properties.organizationId.description: "Organization id; defaults to the credential organization when omitted"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools19 added, 10 changed.+19 added~10 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 54 -> 67.View diff
    • Tools that change things, listed without credentials: 54 to 67
  3. Tools5 added, 2 changed.+5 added~2 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 51 -> 54.View diff
    • Tools that change things, listed without credentials: 51 to 54

Install

Pinned to version 0.14.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http tasklite https://mcp.tasklite.net/mcp
claude mcp add --transport http tasklite https://mcp.tasklite.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tasklite__list_organizations",
      "mcp__tasklite__get_email_usage",
      "mcp__tasklite__list_projects",
      "mcp__tasklite__list_boards",
      "mcp__tasklite__get_board_schema",
      "mcp__tasklite__query_items",
      "mcp__tasklite__get_cells",
      "mcp__tasklite__list_comments",
      "mcp__tasklite__list_uploaded_files",
      "mcp__tasklite__list_signature_requests",
      "mcp__tasklite__get_signature_request",
      "mcp__tasklite__list_telephony_providers",
      "mcp__tasklite__get_telephony_connection",
      "mcp__tasklite__preview_telephony_sync",
      "mcp__tasklite__list_app_endpoints",
      "mcp__tasklite__google_calendar_status",
      "mcp__tasklite__google_calendar_list_events",
      "mcp__tasklite__list_app_users",
      "mcp__tasklite__list_app_invites",
      "mcp__tasklite__list_app_user_links",
      "mcp__tasklite__list_app_roles",
      "mcp__tasklite__list_app_role_grants",
      "mcp__tasklite__get_policy_identity",
      "mcp__tasklite__get_board_policy",
      "mcp__tasklite__get_permission_history",
      "mcp__tasklite__explain_access",
      "mcp__tasklite__get_item_history",
      "mcp__tasklite__list_automations",
      "mcp__tasklite__list_apps",
      "mcp__tasklite__get_app_spec",
      "mcp__tasklite__get_frontend_prompt",
      "mcp__tasklite__search",
      "mcp__tasklite__fetch",
      "mcp__tasklite__list_deployments",
      "mcp__tasklite__get_deployment_files"
    ],
    "ask": [
      "mcp__tasklite__configure_external_access",
      "mcp__tasklite__create_project",
      "mcp__tasklite__create_board",
      "mcp__tasklite__create_column",
      "mcp__tasklite__update_board",
      "mcp__tasklite__update_column",
      "mcp__tasklite__reorder_columns",
      "mcp__tasklite__export_project",
      "mcp__tasklite__create_item",
      "mcp__tasklite__update_item",
      "mcp__tasklite__set_cell",
      "mcp__tasklite__set_cells_if_unchanged",
      "mcp__tasklite__add_comment",
      "mcp__tasklite__update_comment",
      "mcp__tasklite__request_file_upload",
      "mcp__tasklite__create_signature_request",
      "mcp__tasklite__signature_link",
      "mcp__tasklite__start_telephony_connection",
      "mcp__tasklite__test_telephony_connection",
      "mcp__tasklite__configure_telephony_mapping",
      "mcp__tasklite__run_telephony_sync",
      "mcp__tasklite__create_app",
      "mcp__tasklite__push_status",
      "mcp__tasklite__send_test_push",
      "mcp__tasklite__publish_app",
      "mcp__tasklite__create_app_endpoint",
      "mcp__tasklite__update_app_endpoint",
      "mcp__tasklite__google_calendar_connect",
      "mcp__tasklite__google_calendar_set_return_path",
      "mcp__tasklite__google_calendar_ensure_calendar",
      "mcp__tasklite__google_calendar_create_event",
      "mcp__tasklite__google_calendar_update_event",
      "mcp__tasklite__google_calendar_busy",
      "mcp__tasklite__configure_app_settings",
      "mcp__tasklite__add_app_user",
      "mcp__tasklite__create_app_invite",
      "mcp__tasklite__check_invite_code",
      "mcp__tasklite__link_app_user",
      "mcp__tasklite__define_app_role",
      "mcp__tasklite__grant_app_role",
      "mcp__tasklite__set_policy_identity",
      "mcp__tasklite__simulate_request",
      "mcp__tasklite__create_app_api_key",
      "mcp__tasklite__build_backend",
      "mcp__tasklite__create_automation",
      "mcp__tasklite__update_automation",
      "mcp__tasklite__deploy_frontend",
      "mcp__tasklite__rollback_deployment"
    ],
    "deny": [
      "mcp__tasklite__delete_board",
      "mcp__tasklite__delete_project",
      "mcp__tasklite__delete_column",
      "mcp__tasklite__delete_item",
      "mcp__tasklite__delete_comment",
      "mcp__tasklite__void_signature_request",
      "mcp__tasklite__disconnect_telephony",
      "mcp__tasklite__revoke_upload_link",
      "mcp__tasklite__delete_app_endpoint",
      "mcp__tasklite__google_calendar_disconnect",
      "mcp__tasklite__google_calendar_delete_event",
      "mcp__tasklite__set_app_user_role",
      "mcp__tasklite__remove_app_user",
      "mcp__tasklite__revoke_app_invite",
      "mcp__tasklite__unlink_app_user",
      "mcp__tasklite__delete_app_role",
      "mcp__tasklite__revoke_app_role",
      "mcp__tasklite__set_board_policy",
      "mcp__tasklite__delete_board_policy"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tasklite. Review it before you use it.

Capability tags behind 36 rules
  • mcp__tasklite__get_email_usage private-data, untrusted-input
  • mcp__tasklite__get_cells private-data
  • mcp__tasklite__list_comments private-data, untrusted-input
  • mcp__tasklite__add_comment outbound
  • mcp__tasklite__update_comment outbound
  • mcp__tasklite__request_file_upload untrusted-input
  • mcp__tasklite__list_uploaded_files private-data, untrusted-input
  • mcp__tasklite__create_signature_request untrusted-input, outbound
  • mcp__tasklite__list_signature_requests private-data
  • mcp__tasklite__get_signature_request private-data, untrusted-input
  • mcp__tasklite__signature_link untrusted-input
  • mcp__tasklite__test_telephony_connection untrusted-input
  • mcp__tasklite__configure_telephony_mapping outbound
  • mcp__tasklite__preview_telephony_sync untrusted-input
  • mcp__tasklite__run_telephony_sync untrusted-input, outbound
  • mcp__tasklite__send_test_push untrusted-input, outbound
  • mcp__tasklite__publish_app outbound
  • mcp__tasklite__google_calendar_status private-data
  • mcp__tasklite__google_calendar_connect private-data
  • mcp__tasklite__google_calendar_disconnect untrusted-input
  • mcp__tasklite__google_calendar_ensure_calendar private-data, untrusted-input
  • mcp__tasklite__google_calendar_list_events private-data, untrusted-input
  • mcp__tasklite__google_calendar_create_event untrusted-input, outbound
  • mcp__tasklite__google_calendar_update_event untrusted-input, outbound
  • mcp__tasklite__google_calendar_delete_event untrusted-input
  • mcp__tasklite__google_calendar_busy untrusted-input, outbound
  • mcp__tasklite__add_app_user outbound
  • mcp__tasklite__check_invite_code outbound
  • mcp__tasklite__simulate_request outbound
  • mcp__tasklite__create_automation untrusted-input
  • mcp__tasklite__get_app_spec untrusted-input
  • mcp__tasklite__fetch untrusted-input
  • mcp__tasklite__deploy_frontend untrusted-input
  • mcp__tasklite__list_deployments untrusted-input
  • mcp__tasklite__get_deployment_files private-data, untrusted-input
  • mcp__tasklite__rollback_deployment untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.tasklite/mcp/verify?hash=24e3db53237c0187e62ca061345057c4afffa63dcc6b51ae44f7e62917a417e3" | jq -e '.changed == false'

Pinned hash 24e3db53237c, from Nov 18, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.tasklite/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.tasklite/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/net.tasklite/mcp.svg)](https://radar.anlyon.com/servers/net.tasklite/mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.

TaskLite MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TaskLite MCP server safe?

No scan can promise that. What its definitions show: 102 tools, 67 of which can change, send or delete something, and 91 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TaskLite MCP server delete data?

Yes. 19 tools can delete, cancel or revoke something: delete_board, delete_project, delete_column, delete_item, delete_comment, void_signature_request and 13 more.

Can the TaskLite MCP server do things that cannot be undone?

Yes. 9 tools can send, pay, publish or merge: create_signature_request, configure_telephony_mapping, run_telephony_sync, send_test_push, publish_app, google_calendar_create_event and 3 more.

What tools does the TaskLite MCP server have?

102 tools: 19 destructive, 9 irreversible, 39 write, 35 read. delete_board, delete_project, delete_column, delete_item, delete_comment, void_signature_request, disconnect_telephony, revoke_upload_link and 94 more.

Does the TaskLite MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TaskLite MCP server send data to outside services?

13 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): add_comment, update_comment, create_signature_request, configure_telephony_mapping, run_telephony_sync, send_test_push and 7 more.

Has the TaskLite MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.