Please submit feature requests through our support page.
Is your feature request related to a problem? Please describe.
Currently, when an AI Agent (via the Firebase MCP server) invokes the firebase_login tool, it provides a login URL to the user. However, the AI agent often does not output the Session ID by default unless explicitly asked. This creates a security vulnerability (phishing risk) because the user cannot verify if the Session ID on the web browser matches the terminal/MCP session before granting access.
Describe the solution you'd like
Modify the MCP system prompt/instructions for the firebase_login tool so that it strongly instructs the AI to always output the generated Session ID to the user alongside the login link.
For example, the tool description could add:
"CRITICAL: You MUST explicitly output the Session ID to the user in your response so they can verify it on the authentication page."
Describe alternatives you've considered
Users manually adding a custom rule to their local agents (e.g., AGENTS.md) to enforce this behavior, but this should be a default security standard built into the MCP tool schema.
Additional context
Ensuring the Session ID is verified by default protects users from inadvertently approving malicious authentication requests if the AI agent is compromised or acting unpredictably.
Please submit feature requests through our support page.
Is your feature request related to a problem? Please describe.
Currently, when an AI Agent (via the Firebase MCP server) invokes the
firebase_logintool, it provides a login URL to the user. However, the AI agent often does not output theSession IDby default unless explicitly asked. This creates a security vulnerability (phishing risk) because the user cannot verify if the Session ID on the web browser matches the terminal/MCP session before granting access.Describe the solution you'd like
Modify the MCP system prompt/instructions for the
firebase_logintool so that it strongly instructs the AI to always output the generated Session ID to the user alongside the login link.For example, the tool description could add:
"CRITICAL: You MUST explicitly output the Session ID to the user in your response so they can verify it on the authentication page."
Describe alternatives you've considered
Users manually adding a custom rule to their local agents (e.g.,
AGENTS.md) to enforce this behavior, but this should be a default security standard built into the MCP tool schema.Additional context
Ensuring the Session ID is verified by default protects users from inadvertently approving malicious authentication requests if the AI agent is compromised or acting unpredictably.