DBMcp

CRITICAL: Database credentials (usernames and passwords) are hardcoded directly into 'connections.json' as plain text. This file is likely committed to the repository, representing a severe exposure of sensitive information. The 'execute_query' tool allows direct execution of arbitrary SQL (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP) provided by an AI, with only a weak blacklist for specific dangerous operations (like 'DROP DATABASE' or 'TRUNCATE'). This makes the server highly vulnerable to SQL injection, unauthorized data manipulation, and schema destruction if the AI's input is compromised or crafted maliciously. There is no explicit authentication or authorization layer implemented for AI clients interacting with the server's tools, relying solely on the underlying MCP transport's security (which is 'stdio' for local clients in the provided configuration, but can change).