diff --git a/en/guides/application-publishing/publish-mcp.mdx b/en/guides/application-publishing/publish-mcp.mdx
index 95a774f3..df3d47a0 100644
--- a/en/guides/application-publishing/publish-mcp.mdx
+++ b/en/guides/application-publishing/publish-mcp.mdx
@@ -12,6 +12,10 @@ Dify now supports exposing your applications as [MCP](https://modelcontextprotoc
 
 Navigate to your application's configuration interface in Dify, you'll find an MCP Server configuration module. The feature is disabled by default. When you toggle it on, Dify generates an unique MCP Server address for your application. This address serves as the connection point for external tools.
 
+<Danger>
+  Your MCP Server URL contains authentication credentials, so treat it like an API key. If you suspect it's been compromised, use the regenerate button to create a new URL. The old one will immediately stop working.
+</Danger>
+
 <img
   src="/images/CleanShot2025-07-07at08.18.02.png"
   alt="CleanShot 2025-07-07 at 08.18.02.png"
@@ -42,9 +46,6 @@ Simply replace the URL with your Dify app's MCP Server address. Cursor will auto
 
 ## Practical Considerations
 
-- Access Control
-
-  Your MCP Server URL contains authentication credentials, so treat it like an API key. If you suspect it's been compromised, use the regenerate function in Dify to create a new URL. The old one will immediately stop working.
 - Descriptiveness
 
   When designing descriptions for your tool and its input parameters, think about how an AI would interpret them. Clear, specific descriptions lead to better invocations. Instead of "input data," specify "JSON object containing user profile with required fields: name, email, preferences."