Skip to main content

Tool change watch

MCP servers can add, remove or change tools. Quilr checks each server's tool list every hour. With the default setting, it tells you what changed so you can review new or changed tools before your users get them.

Go toQuilrAI consoleSettingsAI GatewayMCP Gatewayserver cardConfigureTools

The Upstream tool changes card sits above the tool list.

Choose what happens​

Pick an option in When the upstream tool list changes, then click Save settings.

OptionWhat happens
Tell me about changes (default)Quilr checks hourly and flags changes here for you to apply. Your clients see the old tool list until you approve.
Update tools automaticallyQuilr checks hourly and applies the new tool list automatically.
Don't watch this MCPQuilr stops checking this MCP for tool changes.

Last checked shows when Quilr last compared the list. Click Check now to compare immediately.

Review a change​

When a change is waiting, the card says This MCP changed N tools upstream. What your clients see is unchanged until you approve it. The change is listed in three parts.

ListWhat it shows
New upstreamTools the server added. Hover a name to read its description.
Gone from upstreamTools the server no longer offers.
Changed upstreamTools whose Description or Input schema changed, with the removed words struck through and the added words highlighted.

An Added risk note summarizes what the change could expose. It is written by an AI model, so read the change itself before you decide.

ButtonResult
ApproveYour clients receive the new tool list immediately.
DismissThe tool list stays as it is. A different change is flagged again.

Approve and Dismiss take effect immediately; you don't need to save. A newly approved tool is enabled like any other tool, so turn off or require confirmation for it in the tool list if needed.

Servers that can't be watched​

Quilr can only check servers it can reach with its own credentials. For these servers the card says why it isn't watching:

ServerCard message
OAuth servers where each user signs inThis MCP signs in per user; refresh it from the console.
OAuth passthrough serversThis MCP passes each client's own upstream token through.
Servers where each user brings their own API keyConnect this MCP with your own upstream API key before using it.
API MCPsThis API MCP's tools come from its gateway API configuration.

For these, click Refresh tools in the Tools section to fetch the current list whenever you need it.