fetchCatalog
Fetches the complete product catalog with all available items
This record as markdown: /tools/firebase-genkit/fetchcatalog.md
What fetchCatalog does on Genkit MCP
AI agents call fetchCatalog to retrieve information from Genkit MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fetchCatalog is rated Low
The tool retrieves product catalog information from what appears to be a product database or system. The verb 'fetches' and the passive nature of accessing existing catalog data (with no mention of creating, updating, deleting, or triggering external operations) clearly classify this as a Read operation.
From the tool's definition Tool name 'fetchCatalog' and description 'Fetches the complete product catalog with all available items' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs fetchCatalog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genkit MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetchCatalog, this is the rule to start with:
fetchCatalog is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genkit MCP, apply this rule, and every fetchCatalog call is checked against it from then on.
Questions about fetchCatalog
Fetches the complete product catalog with all available items. It is categorised as a Read tool in the Genkit MCP MCP Server, which means it retrieves data without modifying state.
Register the Genkit MCP server in PolicyLayer and add a rule for fetchCatalog: 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 Genkit MCP. Nothing to install.
fetchCatalog 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 fetchCatalog 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 fetchCatalog. 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.
fetchCatalog is provided by the Genkit MCP server (genkit-ai/genkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genkit, and thousands of servers like it.
This server
Across the catalogue