This record as markdown: /tools/io-github-portel-dev-ncp/create-charge.md
What create_charge does on Ncp
AI agents use create_charge to commit financial operations through Ncp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why create_charge is rated Critical
This tool directly processes payments through Stripe, moving money and committing financial obligations. Financial operations represent the most severe risk category due to potential for unauthorized transactions, fraud, or substantial monetary loss if misused by an AI agent.
From the tool's definition Tool name 'create_charge' and description 'Process a payment charge using Stripe' explicitly indicate financial transaction processing.
Attacks that exploit this kind of access
The rule that runs create_charge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_charge, this is the rule to start with:
Any call to create_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 Ncp, apply this rule, and every create_charge call is checked against it from then on.
Questions about create_charge
Process a payment charge using Stripe. It is categorised as a Financial tool in the Ncp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Ncp MCP server in PolicyLayer and add a rule for create_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 Ncp. Nothing to install.
create_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 create_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 create_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.
create_charge is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
Across the catalogue