Tool manifest changed since last run

What it means

Approving an MCP server is a one-time decision, but the server can change afterwards. It can add a tool that writes or executes, give an existing read-only tool a new "command" or "path" parameter, or rewrite a tool description so it starts instructing the model. None of that triggers a new approval prompt in most clients. patchbay pins the tool manifest the first time it audits a server and diffs against it on later runs. Severity follows the most serious change in the diff: critical: a new write-shaped tool, or a read tool that gained a write-shaped parameter medium: an existing tool's description changed low: an input schema changed structurally, or a new read-only tool appeared info: a tool was removed

How to fix

Review the diff in the finding. If every change is expected because you updated the server on purpose, re-pin the manifest: npx -y @patchbay-nebius/agent audit <url> --trust If a change is unexpected, do not re-pin. Check the server's release notes, or the deployment log for a self-hosted server, before you let an agent call it again.

Background