confirmBooking

Confirm with the user before booking a dish.

SERVERGenkit MCP SOURCEgenkit-ai/genkit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/firebase-genkit/confirmbooking.md

WHAT IT DOES

What confirmBooking does on Genkit MCP

AI agents call confirmBooking 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.

RISK

Why confirmBooking is rated Low

Even though confirmBooking only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs confirmBooking 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 confirmBooking, this is the rule to start with:

confirmBooking Allowed

confirmBooking is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "confirmBooking": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Genkit MCP, apply this rule, and every confirmBooking call is checked against it from then on.

FAQ

Questions about confirmBooking

What does the confirmBooking tool do? +

Confirm with the user before booking a dish. It is categorised as a Read tool in the Genkit MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on confirmBooking? +

Register the Genkit MCP server in PolicyLayer and add a rule for confirmBooking: 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.

What risk level is confirmBooking? +

confirmBooking is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit confirmBooking? +

Yes. Add a rate_limit block to the confirmBooking 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.

How do I block confirmBooking completely? +

Set action: deny in the PolicyLayer policy for confirmBooking. 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.

What MCP server provides confirmBooking? +

confirmBooking 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.

KEEP EXPLORING

More on Genkit, and thousands of servers like it.

This server

All 72 Genkit tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →