datePicker
user can use this UI tool to enter a date (prefer this over asking the user to enter the date manually)
This record as markdown: /tools/firebase-genkit/datepicker.md
What datePicker does on Genkit MCP
AI agents call datePicker as a supporting operation in Genkit MCP workflows.
Why datePicker is rated Low
The datePicker tool is a UI interaction component that allows a user to input a date. It does not read from a data store, write or modify persistent data, execute code, perform destructive actions, or involve financial transactions. It is purely a user-facing input mechanism, placing it in the 'Other' category. Severity is low as misuse has minimal blast radius — at worst, an incorrect date is submitted.
From the tool's definition 'user can use this UI tool to enter a date' — this is a UI input widget that captures a date value from the user, with no data retrieval, modification, execution, or financial action described
Attacks that exploit this kind of access
The rule that runs datePicker 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 datePicker, this is the rule to start with:
datePicker gets a rate cap, and 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 datePicker call is checked against it from then on.
Questions about datePicker
user can use this UI tool to enter a date (prefer this over asking the user to enter the date manually). It is categorised as a Other tool in the Genkit MCP MCP Server, which means it performs auxiliary operations.
Register the Genkit MCP server in PolicyLayer and add a rule for datePicker: 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.
datePicker is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the datePicker 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 datePicker. 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.
datePicker 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