test_gateway · Rebillia MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_gateway does on Rebillia MCP Server

AI agents invoke test_gateway to trigger actions in Rebillia MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why test_gateway needs a policy

Testing a gateway connection is not a simple read; it actively initiates an external network operation against the payment gateway to verify connectivity. This falls under Execute as it triggers an external operation whose effects depend on arguments (the gatewayId). It is not purely Read since it performs an active connection test rather than just retrieving stored data.

From the tool's definition 'Test gateway connection' - triggers an external operation against a payment gateway endpoint to verify connectivity and returns connection status

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_gateway Rate-limited

test_gateway stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_gateway": {
      "limits": [
        {
          "counter": "test_gateway_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rebillia MCP Server, so you can run agents against it safely.

FAQ

Questions about test_gateway

What does the test_gateway tool do? +

Test gateway connection. GET /gateways/{gatewayId}/test. Returns the gateway object with connection status (e.g. status active on success). It is categorised as a Execute tool in the Rebillia MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_gateway? +

Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for test_gateway: 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 Rebillia MCP Server. Nothing to install.

What risk level is test_gateway? +

test_gateway is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_gateway? +

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

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

test_gateway is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.