AI agents call firebase_list_projects 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.
The tool retrieves and lists Firebase projects belonging to the authenticated user. This is a read-only operation that queries data without modifying, deleting, or executing any operations. The blast radius is minimal—an AI agent misusing this tool would only gain visibility into the user's project inventory, not modify or delete anything.
From the tool's definition Tool name contains 'list' and description indicates '내 Firebase 프로젝트 목록 조회' (list my Firebase projects). This is a query/retrieval operation with no 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_list_projects: 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_list_projects 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_list_projects 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_list_projects. 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_list_projects 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_list_projects 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 →