List all Cloud Functions in the project
AI agents call list_functions to retrieve information from Firebase Live MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about Cloud Functions without modifying, deleting, or executing them. However, the information disclosed (all functions in a project) could be sensitive for reconnaissance purposes, justifying medium severity if misused by an agent to map infrastructure. Read category is appropriate because the operation is fundamentally a query that does not alter state.
From the tool's definition Tool name is 'list_functions' and description states 'List all Cloud Functions in the project' — a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
List all Cloud Functions in the project. It is categorised as a Read tool in the Firebase Live MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firebase Live 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 Live 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 Live MCP Server MCP server (nigelthorne/firebase_live_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 →