[KomachiSion]

What is the purpose of the change

Backport the configurable MCP tool import endpoint policy from #15746 to the 3.2.4 maintenance line. This gives operators predictable control over outbound tool-import connections while keeping public MCP endpoints available by default.

Brief changelog

• Add a global switch for Console MCP tool imports.
• Allow public targets by default and require an administrator-managed IP/CIDR list for private or local targets.
• Validate the base URL and relative endpoint, and disable redirects.
• Surface backend rejection messages in the Console UI.
• Add English and Chinese specifications, unit tests, and target-native OpenAPI coverage.

Verifying this change

• mvn -pl console,test/openapi-test spotless:apply
• mvn -pl console,test/openapi-test spotless:check
• mvn -pl console -Dtest=McpEndpointAccessValidatorTest,ConsoleMcpControllerTest test (23 tests passed)
• mvn -pl test/openapi-test -DskipTests test-compile
• Console UI build and targeted ESLint; packaged static assets match the frontend build output.
• mvn -B clean compile apache-rat:check checkstyle:check spotbugs:check spotless:check -e -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn (60 modules passed)

Follow this checklist to help us incorporate your contribution quickly and easily:

• This maintenance backport follows the already merged Add outbound access controls for MCP tool import #15746; no separate public issue is associated with it.
• Each commit in the pull request has a meaningful subject line and body.
• The pull request description explains what the change does, how, and why.
• Unit tests and OpenAPI integration-test coverage are included.
• The effective CI compile and quality checks pass locally.

[github-actions]

Thanks for your this PR. 🙏
Please check again for your PR changes whether contains any usage/api/configuration change such as Add new API , Add new configuration, Change default value of configuration.
If so, please add or update documents(markdown type) in docs/next/ for repository nacos-group/nacos-group.github.io

---

感谢您提交的PR。 🙏
请再次查看您的PR内容，确认是否包含任何使用方式/API/配置参数的变更，如：新增API、新增配置参数、修改默认配置等操作。
如果是，请确保在提交之前，在仓库nacos-group/nacos-group.github.io中的docs/next/目录下添加或更新文档（markdown格式）。