Option to keep secrets out of MCP responses

When an AI assistant uses the Easypanel MCP server, read-only procedures return credentials in plain text. For example, listProjectsAndServices returns every service's environment variables, database passwords, service deploy tokens and DB Gate tokens, for all projects. The assistant only needed project and service names, but every secret on the server ended up in the chat transcript.

AI agents and integrations usually need to see structure, not secrets, and they keep long-lived logs and transcripts.

Proposal 1

Add an option to the MCP server that removes environment variables and secrets from its scope.

Example:

• https://easypanel.example.com/api/mcp: current behavior
• https://easypanel.example.com/api/mcp/safe: same procedures, with env values, passwords and tokens removed or masked

Proposal 2

Remove or mask environment variables and secrets in all MCP responses. Move reading and updating env vars and credentials to a separate service or tool, with its own permissions, so it can be granted only when needed.

This would let people connect AI assistants to Easypanel for day-to-day operations without exposing every credential on the server.