woo_payment_gateways_get

Get a payment gateway

SERVERCowork Bench SOURCE0717376/cowork_bench

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-bench/woo-payment-gateways-get.md

WHAT IT DOES

What woo_payment_gateways_get does on Cowork Bench

AI agents call woo_payment_gateways_get to retrieve information from Cowork Bench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why woo_payment_gateways_get is rated Low

Even though woo_payment_gateways_get only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs woo_payment_gateways_get 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_get, this is the rule to start with:

woo_payment_gateways_get Allowed

woo_payment_gateways_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "woo_payment_gateways_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every woo_payment_gateways_get call is checked against it from then on.

FAQ

Questions about woo_payment_gateways_get

What does the woo_payment_gateways_get tool do? +

Get a payment gateway. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on woo_payment_gateways_get? +

Register the Cowork Bench MCP server in PolicyLayer and add a rule for woo_payment_gateways_get: 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_get? +

woo_payment_gateways_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit woo_payment_gateways_get? +

Yes. Add a rate_limit block to the woo_payment_gateways_get 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_get completely? +

Set action: deny in the PolicyLayer policy for woo_payment_gateways_get. 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_get? +

woo_payment_gateways_get 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.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →