Create or retrieve a setup intent via the gateway endpoint. Use only as part of a gateway-agnostic payment method flow: the returned setupIntent.id can be used as paymentMethodNonce for create_customer_payment_method. No raw card data.
AI agents use create_setup_intent to commit financial operations through Rebillia MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
A setup intent in payment gateways (e.g., Stripe) is a financial operation that authorizes future charges against a customer's payment method. Creating one establishes a financial commitment path. Misuse could enable unauthorized payment method registration, leading to fraudulent charges. This falls under Financial as it directly enables future money movement.
From the tool's definition 'Create or retrieve a setup intent via the gateway endpoint' and 'setupIntent.id can be used as paymentMethodNonce for create_customer_payment_method' — this initiates a payment method setup flow tied to billing infrastructure
Attacks that exploit this kind of access
Create or retrieve a setup intent via the gateway endpoint. Use only as part of a gateway-agnostic payment method flow: the returned setupIntent.id can be used as paymentMethodNonce for create_customer_payment_method. No raw card data. It is categorised as a Financial tool in the Rebillia MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for create_setup_intent: 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 Rebillia MCP Server. Nothing to install.
create_setup_intent 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 create_setup_intent 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 create_setup_intent. 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.
create_setup_intent is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-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 →