We are experiencing the same issue.
Would be great if this could be (possibly optionally) turned off as most open source MCP tools are not built to work with these four parameters.
Now it is possible to change the code of the MCP server such that it can work with them, I did this for Zabbix (see: Add optional n8n AI Agent metadata fields to all tool definitions to prevent Pydantic "unexpected keyword argument" errors by lucmatisse · Pull Request #27 · mpeirone/zabbix-mcp-server · GitHub). But it is not ideal to have to change this for every MCP tool that we would like to use as this is quite time intensive and might interfere with the functionality of some MCP Servers as well.