New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

woo_payment_gateways_update

Update a payment gateway

SERVERCowork Bench SOURCE0717376/cowork_bench
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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'

Questions about woo_payment_gateways_update

What does the woo_payment_gateways_update tool do? +

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.

How do I enforce a policy on woo_payment_gateways_update? +

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.

What risk level is woo_payment_gateways_update? +

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.

Can I rate-limit woo_payment_gateways_update? +

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.

How do I block woo_payment_gateways_update completely? +

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.

What MCP server provides woo_payment_gateways_update? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cowork Bench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.