This record as markdown: /tools/firebase-genkit/processpayment.md
What processPayment does on Genkit MCP
AI agents use processPayment to commit financial operations through Genkit MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why processPayment is rated Critical
This tool directly handles payment processing, which involves the transfer of funds or creation of financial obligations. This is the most severe category (Financial > Destructive > Execute > Write > Read). A misused payment processor could result in unauthorized charges, duplicate transactions, or financial loss. Critical severity is appropriate given the direct financial impact and potential for significant harm.
From the tool's definition Tool name 'processPayment' with description 'Process a payment for an order' explicitly indicates moving money or committing financial obligations.
Attacks that exploit this kind of access
The rule that runs processPayment 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 processPayment, this is the rule to start with:
Any call to processPayment is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Genkit MCP, apply this rule, and every processPayment call is checked against it from then on.
Questions about processPayment
Process a payment for an order. It is categorised as a Financial tool in the Genkit MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Genkit MCP server in PolicyLayer and add a rule for processPayment: 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.
processPayment is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the processPayment 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 processPayment. 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.
processPayment 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.
Across the catalogue