crm_report_billing
Report a payment to the CRM billing webhook. Activates or deactivates a marketplace app for a location based on payment status. Required for external billing (SaaS subscriptions through Stripe).
This record as markdown: /tools/io-github-0nork-0nmcp/crm-report-billing.md
What crm_report_billing does on 0nmcp
AI agents use crm_report_billing to commit financial operations through 0nmcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why crm_report_billing is rated Critical
This tool directly handles financial transactions by reporting payments and controlling subscription/billing state (activate/deactivate) for SaaS subscriptions via Stripe. Misuse could trigger fraudulent payment reports, unauthorized app activations, or disrupt legitimate billing — making it a Financial category tool with critical severity.
From the tool's definition Report a payment to the CRM billing webhook. Activates or deactivates a marketplace app for a location based on payment status. Required for external billing (SaaS subscriptions through Stripe).
Attacks that exploit this kind of access
The rule that runs crm_report_billing 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_report_billing, this is the rule to start with:
Any call to crm_report_billing 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_report_billing call is checked against it from then on.
Questions about crm_report_billing
Report a payment to the CRM billing webhook. Activates or deactivates a marketplace app for a location based on payment status. Required for external billing (SaaS subscriptions through Stripe). 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_report_billing: 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_report_billing 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_report_billing 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_report_billing. 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_report_billing 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