search_versions
AI agents call search_versions to retrieve information from Firebase DAM 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 version data from Firebase Firestore without any mechanism to create, modify, delete, or execute arbitrary operations. The server's documented purpose is read-only access to DAM collections, and search operations have no side effects. Severity is low because retrieving version metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Server description emphasizes 'read-only access' and the tool name 'search_versions' indicates a query/search operation with no modification capabilities. Sibling tools (search_asset_files, search_assets, search_comments) are all Read category operations.
Attacks that exploit this kind of access
search_versions. It is categorised as a Read tool in the Firebase DAM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firebase DAM MCP Server MCP server in PolicyLayer and add a rule for search_versions: 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 DAM MCP Server. Nothing to install.
search_versions 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 search_versions 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 search_versions. 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.
search_versions is provided by the Firebase DAM MCP Server MCP server (lt012071/dam-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 →