crm_marketplace_charge
Charge a location for an add-on or service through the CRM marketplace billing. The CRM handles payment collection from the sub-account owner.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-marketplace-charge.md
What crm_marketplace_charge does on 0nmcp
AI agents use crm_marketplace_charge to commit financial operations through 0nmcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why crm_marketplace_charge is rated Critical
This tool moves money by charging customers through a CRM marketplace billing system. It commits financial obligations (payments for add-ons/services) and transfers funds. Financial category takes precedence over all others per severity hierarchy. Critical severity due to high blast radius: an AI agent with unrestricted access could charge arbitrary amounts to arbitrary locations, causing direct financial harm.
From the tool's definition Tool name includes 'charge'; description states 'Charge a location for an add-on or service' and 'payment collection'. These terms directly indicate money movement and financial obligations.
Attacks that exploit this kind of access
The rule that runs crm_marketplace_charge 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_marketplace_charge, this is the rule to start with:
Any call to crm_marketplace_charge 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_marketplace_charge call is checked against it from then on.
Questions about crm_marketplace_charge
Charge a location for an add-on or service through the CRM marketplace billing. The CRM handles payment collection from the sub-account owner. 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_marketplace_charge: 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_marketplace_charge 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_marketplace_charge 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_marketplace_charge. 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_marketplace_charge 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