AI agents call firebase_get_project 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 or queries Firebase project configuration and metadata. The verb 'get' and the explicit retrieval semantics confirm a Read operation. No data is created, modified, deleted, or executed. The blast radius is minimal as it only exposes project configuration details that are typically not sensitive in the context of project management.
From the tool's definition Tool name 'firebase_get_project' and description 'Firebase 프로젝트 상세 정보 조회' (Firebase project detailed information retrieval) indicate data retrieval without side effects.
Attacks that exploit this kind of access
Firebase 프로젝트 상세 정보 조회. 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_project: 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_project 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_project 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_project. 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_project 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_project 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 →