The connector is built so that you see and approve what changes, and so that it can't do more than you can do yourself in the PATHwd web app.
The connector's tools are split by what they do, and each carries the standard MCP hints your app uses to decide when to ask you before a call:
| Group | Hints | Examples |
|---|---|---|
| Read | readOnlyHint: true | finding records, reading notes, running a report |
| Add | readOnlyHint: false, destructiveHint: false | creating a record, adding a note, uploading a file |
| Change | destructiveHint: true | changing a field, running a pathway, completing a task |
| Remove | destructiveHint: true | archiving a record, deleting a file, deleting a calendar event |
openWorldHint: true | sending an email from a record to people outside PATHwd |
In Claude, read-only tools can run without asking each time and tools marked destructive ask before each call; your own connector settings can change this per tool. ChatGPT and Codex also use these hints together with your settings. The full list is in the tools reference.
Each tool runs only its own commands. A request that tries to run another tool's command through a tool is refused and names the right tool, so a read tool can never be used to make a change.
Every command that deletes something permanently works in two steps:
NOT DELETED: this needs confirmation., names exactly what would be deleted (for example the file name and the record it is on, or the calendar event, when it starts and the appointment field it would clear), and gives a code such as DEL-1A2B3C4D.Before giving a code, the command checks your access: if the web app wouldn't let you delete it, you are told so and no code is given. There is no option that skips the confirmation.
The PATHwd documentation that comes with the connector describes showing you what will be deleted and waiting for your explicit yes before the second call. And because the remove tools are marked destructive, Claude asks for your approval before each of those calls as well.
Commands that ask for a code: deleting a file, a note or a message from a record; deleting a calendar, a calendar group or a calendar event; clearing a record's appointment field; deleting a folder's own sticker or resetting a folder's stickers; deleting a report's Custom Field.
These don't ask for a code because they can be undone or are routine in the web app:
| Action | How it is undone |
|---|---|
| Archive a record | Unarchive it (path_update_record, unarchive-record) |
| Archive a file | Unarchive it (path_update_record, unarchive-record-file) |
| Unlink two records | Link them again (path_create_record, link-record) |
| Cancel a task | A cancelled task can't be reopened; a new task can be created |
They are still in the remove tools, marked destructive, so your app treats them like the other removals.
path_send_email sends a real email from a record, as you: it goes out from your name and PATHwd email address to the recipients given, CCs the record's own address, and is saved to the record's Emails list. A sent email can't be recalled.
openWorldHint: true because the email reaches people outside PATHwd, so your app can ask you before it is used.--preview) that shows exactly what would be sent (sender, recipients, subject, body and attachments) without sending or uploading anything. The PATHwd documentation that comes with the connector describes previewing first and sending only after you approve the recipients and content.Some requests are refused for everyone, whatever the account or role:
| Request | What happens |
|---|---|
A raw API call (the PATH CLI's api command), in any tool or spelling | Refused: only the PATH CLI's own commands run on the connector |
Pointing commands at another server (--base-url) | Refused: the PATHwd API address is fixed |
Signing in or out from the chat (auth, logout) | Refused: sign-in happens when you connect, sign-out when you disconnect |
Reading or writing files outside your private workspace (absolute paths, ~, ..) | Refused: commands only see files in the workspace |
Reading from standard input (--in -) | Refused |
JSON output (--json) | Refused: results come back as compact text |
Pathway test tooling (pathway-run test, save-test, cleanup, delete) | Not available on the connector |
| Changing the account's design (business objects, fields, workflow, pathway steps) | Not available on the connector |
And some depend on who you are:
| Request | Who may | Everyone else |
|---|---|---|
Acting as another member (--as-user) | Account Admins | Refused: "… can't use --as-user: acting as another user is the web's Impersonate, which only account Admins have." |
| Starting a pathway on a record its rules would hide it on (super-user mode) | Users with Designer permission | Refused |
| Anything the web app wouldn't let you do | As in the web app | Refused: "… can't … — …, as in the web app." |
Records contain text written by other people: customer names, notes, emails, messages. An assistant reading that text could be misled by instructions hidden in it. The connector limits the effect: it can only do what you can do, permanent deletes need a confirmation code, and your app asks before changes and emails. Read what the assistant proposes before you approve it.
If you have any questions, concerns, or requests related to our privacy policy, please contact us.