List all Cloud Functions registered in the emulator
AI agents call list_functions to retrieve information from Firebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries and returns a list of available Cloud Functions without invoking them or modifying their configuration. It has no side effects and fits squarely in the Read category. Severity is low because listing functions exposes information about available operations but does not execute code or modify data.
From the tool's definition Tool lists Cloud Functions registered in the emulator. Described as 'List all' which is a read-only enumeration operation. No mutation, deletion, or execution of functions occurs—only retrieval of their metadata.
Attacks that exploit this kind of access
List all Cloud Functions registered in the emulator. It is categorised as a Read tool in the Firebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firebase MCP Server MCP server in PolicyLayer and add a rule for list_functions: 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 Firebase MCP Server. Nothing to install.
list_functions 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 list_functions 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 list_functions. 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.
list_functions is provided by the Firebase MCP Server MCP server (nigelthorne/firebase_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →