Question: should MCP tool changes trigger re-approval?

[MaazAhmed47]

Hi Julien, small MCP security/design question.

Anyquery is interesting here because it lets LLM clients query files, databases, apps, and other data sources through MCP.

When a tool has already been approved by a user or operator, should later changes to the tool surface be treated as a re-approval event?

Examples:

• schema changes
• new required parameters
• broader data access
• new external reach
• read-only behavior becoming write/export/delete
• auth scope expansion

I’m trying to understand how MCP builders handle this today.

For a project like Anyquery, would this usually be treated as normal versioning, client behavior, gateway behavior, or something the MCP server should signal explicitly?