crm_create_payment_config
Configure payment processing (Stripe) for a CRM location. This wires Stripe into the location so it can accept payments natively.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-create-payment-config.md
What crm_create_payment_config does on 0nmcp
AI agents use crm_create_payment_config to commit financial operations through 0nmcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why crm_create_payment_config is rated Critical
This tool configures payment processing systems (Stripe integration), which establishes financial transaction capabilities. Misuse by an AI agent could redirect payments, alter payment flows, or compromise financial data integrity. This is a critical financial control that warrants the highest severity classification.
From the tool's definition Tool explicitly performs payment processing configuration: 'Configure payment processing (Stripe)' and 'wires Stripe into the location so it can accept payments natively.' This directly involves financial infrastructure setup.
Attacks that exploit this kind of access
The rule that runs crm_create_payment_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_create_payment_config, this is the rule to start with:
Any call to crm_create_payment_config is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every crm_create_payment_config call is checked against it from then on.
Questions about crm_create_payment_config
Configure payment processing (Stripe) for a CRM location. This wires Stripe into the location so it can accept payments natively. It is categorised as a Financial tool in the 0nmcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the 0n MCP server in PolicyLayer and add a rule for crm_create_payment_config: 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 0nmcp. Nothing to install.
crm_create_payment_config 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 crm_create_payment_config 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 crm_create_payment_config. 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.
crm_create_payment_config is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
Across the catalogue