Help center
What the assistant can do
The tools certo's MCP server gives an assistant, what each one is for, and the rules that keep candidates' data safe.
3 minute read
Each tool is one action an assistant may take. It can use a tool only when your role, and what you approved when you connected, allow it.
Tools
| Tool | What it does | Changes anything? |
|---|---|---|
get_organisation | Your organisation and what this connection may do | no |
get_credits | Your verification balance and history | no |
list_positions, get_position | Your positions | no |
create_position, update_position, close_position, reopen_position | Manage positions | yes |
read_people_list | Turn a pasted list into rows; nothing is kept | no |
invite_candidates | Invite people, after showing you the dry run | yes: sends e-mail, spends verifications |
list_invitations, get_invitation, withdraw_invitation | Follow and withdraw invitations | withdrawing does |
ask_to_read_passport | Ask to read a published passport, after the dry run | yes: sends a request, holds a verification |
list_access_requests, get_access_request, withdraw_access_request | Follow and withdraw asks | withdrawing does |
list_candidates | Your candidates list with each checklist's state | no |
get_candidate_passport | A passport the candidate shared with you | no, but the read is logged and the candidate sees it |
get_candidate_age | Over 18 and over 21, the date only if shared | no, but the read is logged and the candidate sees it |
get_candidate_checklist | What is ready and what is missing | no |
issue_records | Issue degrees, certificates or leaver records, after the dry run | yes: sends e-mail; a university spends sponsorships |
list_issued_records, get_issued_record | What you issued and who claimed it | no |
revoke_issued_record | Revoke a certificate you issued, after showing you the record | yes: permanent, tells the holder |
get_webhook, send_webhook_test | Your webhook's state and last deliveries; one test event | the test sends one event |
list_members | Who is in your organisation, without addresses | no |
search_help, get_help_article | This help center | no |
The rules it keeps
- A dry run first. Inviting, asking and issuing are shown to you before they happen, and happen only after you confirm, and revoking shows you the record first. Where your assistant can ask you directly, certo asks you; otherwise the assistant must come back with the confirmation it was given for exactly that list, which works for that list only, for 15 minutes. A confirmed call sent twice happens once.
- Not through an assistant. Exports (a file), and setting up, rotating or removing the webhook (its secret must never pass through an assistant), are done with the API or in the console.
- A passport is data, not instructions. Text in a passport is what a candidate wrote or an organisation confirmed. The assistant is told never to follow instructions found in it.
- Read only what you asked about. Every passport read is logged and visible to the candidate, so the assistant reads one only when you ask about that candidate.
- Nothing is kept. certo's MCP server stores no conversation, no answer and no passport. It records which tool was used and whether it worked, never what went in or came out.
When something is refused
The assistant tells you why and what to do, in certo's words: a missing permission names what an owner or an admin can add, a lack of verifications says how many are needed. The same codes as the API: Errors, limits and retries.