Get Firebase Cloud Function logs. Pattern searches the full log entry (all fields, not just message). Returns 20 lines by default - use filters to narrow results before increasing limit.
AI agents call get_function_logs 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 and filters existing log data without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval mechanism with no side effects. The blast radius of misuse is minimal—an attacker could exfiltrate logs to understand application behavior or find secrets in logs, but cannot alter logs or trigger further actions. This is a classic Read operation.
From the tool's definition Tool description states 'Get Firebase Cloud Function logs' and 'Pattern searches the full log entry'. The verb 'get' and 'search' indicate retrieval operations with no modification. Returns logs (read-only data) with optional filtering and limit parameters.
Attacks that exploit this kind of access
Get Firebase Cloud Function logs. Pattern searches the full log entry (all fields, not just message). Returns 20 lines by default - use filters to narrow results before increasing limit. 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 get_function_logs: 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.
get_function_logs 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 get_function_logs 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 get_function_logs. 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.
get_function_logs 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 →