AI agents call firebase_get_web_config to retrieve information from Mimi Seed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Firebase configuration data used for web client initialization. The firebaseConfig object is intended to be public (embedded in web frontends) and contains no server secrets or authentication credentials that could grant elevated access. Retrieving this configuration has no side effects and poses minimal security risk, fitting the Read category.
From the tool's definition Tool name contains 'get'; description translates to 'Firebase Web configuration (firebaseConfig object) query/retrieval'.
Attacks that exploit this kind of access
Firebase Web 설정 (firebaseConfig 객체) 조회. It is categorised as a Read tool in the Mimi Seed MCP Server, which means it retrieves data without modifying state.
Register the Mimi Seed MCP server in PolicyLayer and add a rule for firebase_get_web_config: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mimi Seed. Nothing to install.
firebase_get_web_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the firebase_get_web_config rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for firebase_get_web_config. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
firebase_get_web_config is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
firebase_get_web_config is one line of Mimi Seed's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →