This record as markdown: /tools/cowork-bench/woo-payment-gateways-update.md
What woo_payment_gateways_update does on Cowork Bench
AI agents use woo_payment_gateways_update to commit financial operations through Cowork Bench, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why woo_payment_gateways_update is rated Critical
Modifying payment gateway configuration directly affects how financial transactions are processed. An attacker or misconfigured agent could redirect payments, disable legitimate gateways, or enable fraudulent ones, making this a critical financial risk.
From the tool's definition 'woo_payment_gateways_update' and 'Update a payment gateway'
Attacks that exploit this kind of access
The rule that runs woo_payment_gateways_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For woo_payment_gateways_update, this is the rule to start with:
Any call to woo_payment_gateways_update is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every woo_payment_gateways_update call is checked against it from then on.
Questions about woo_payment_gateways_update
Update a payment gateway. It is categorised as a Financial tool in the Cowork Bench MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for woo_payment_gateways_update: 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 Cowork Bench. Nothing to install.
woo_payment_gateways_update 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 woo_payment_gateways_update 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 woo_payment_gateways_update. 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.
woo_payment_gateways_update is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
Across the catalogue