On this page
01
What you'll set up
An MCP server can change what a tool does without telling you. A new description or a new input can change how a model uses it. In about eight minutes you will turn on visibility for a registered server and review a change.
- Tool definitions recorded for each registered server
- The first definition of every tool approved for you
- A side-by-side view when a definition changes
- Approve and Reject decisions in the audit log
You need a registered server and an owner or admin role to review.
02
What Cloptima records
A tool definition is what the model is shown about a tool: its name, its description, and its input schema. Cloptima records the definitions your agents send for registered servers.
| Part of a definition | Why it matters |
|---|---|
| Name | It is how the tool is called and governed |
| Description | It tells the model when and how to use the tool |
| Input schema | It tells the model what arguments to send |
03
Label your tools with their server
To attach a tool to a registered server, the tool needs the server's name as a label.
Add the label in the tool declaration, using the server's registered name. Cloptima reads server, server_name, server_label, tool_server, mcp_server, and mcp_server_name.
{
"type": "function",
"function": {
"name": "search_issues",
"description": "Search Jira issues by text",
"parameters": { "type": "object", "properties": { "query": { "type": "string" } } }
},
"server": "jira"
}Tools that arrive through the provider's own MCP support carry their server label already.
04
The first definition is approved for you
You do not have to approve every tool by hand. The first definition Cloptima sees for a tool is approved automatically, and becomes the one every later change is compared with.
1First seen
Approved automatically
2Seen again
Same definition, last seen updated
3Changed
Shown as Changed, waiting for review
4Reviewed
Approved or rejected
05
Find the tools on a server
Each server in the registry lists the tools Cloptima has observed.
- 1
Open the registry
Go to AI → Credentials & Keys and find the MCP Tool Server Registry card.
- 2
Open the server's tools
Expand the server to see Observed tools: each tool with its status and when it was last seen.
- 3
Read the badges
Approved means the current definition is the one you accepted. New means a tool with no approved definition yet. Changed means the definition differs from the approved one.
2Observed tools
| Tool | Status | Last seen |
|---|---|---|
| search_issues | Approved | Oct 5, 2026 |
| get_issue | Changed | Oct 5, 2026 |
| create_issue | New | Oct 4, 2026 |
2 tool changes to review
A count of tool changes to review appears at the top of the card.
06
Review a change
Choose Review on a Changed tool to see two definitions side by side: the one you approved and the one Cloptima observed.
- 1
Compare
Read the description and the input schema. Look for new arguments, changed wording, or new instructions.
- 2
Approve
Approve if the change is expected. The new definition becomes the approved one, and the old one is marked superseded.
- 3
Reject
Reject if the change is not expected. The decision is recorded.
07
What a review does and does not do
A review is a record and a signal. It tells you when a server changed and what you decided.
| A review does | A review does not |
|---|---|
| Record who decided, and when | Stop requests from using the changed tool |
| Keep the approved version beside the new one | Roll back the server |
| Show up in the audit log | Replace the allow and deny lists |
To stop a tool, use the lists. To act on a change you reject, deny the tool or disable the server.
08
Find the decision in the audit log
Every Approve and Reject is recorded, with the tool name, the server, and who decided.
Open AI → Audit to see them next to the other governance events.
09
A weekly routine
A short routine keeps tool changes from piling up.
- 1
Check the count
Open the registry and read the number of tool changes to review.
- 2
Review each change
Approve the expected ones. Reject the rest.
- 3
Act on rejections
Deny the tool, or disable the server, until you understand the change.
10
If something goes wrong
Most questions are about labels.
| What you see | Likely cause | Fix |
|---|---|---|
| No tool definitions observed for a server | Tools are not labeled with the server's name | Add the server label to the tool declarations |
| A tool never shows up | The label does not match a registered server | Use the registered name exactly |
| A tool shows Changed after every release | Your framework adds fields to the schema | Approve the variant once. Each variant is reviewed once |
| A notice says the limit is reached | The number of stored definitions has reached your plan's allowance | Delete servers you no longer use, or contact us |