run_test_suite · Omise MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_test_suite does on Omise MCP Server

AI agents invoke run_test_suite to trigger actions in Omise 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 run_test_suite needs a policy

This tool triggers execution of code (test suite) which is an Execute category action. Severity is medium rather than high because test suites typically operate in sandboxed/non-production environments, but could still cause side effects depending on what the tests interact with (test data, external services, etc.).

From the tool's definition Tool name 'run_test_suite' and description 'Run comprehensive test suite' indicate execution of arbitrary test code. Within a payment processing context (Omise MCP Server), this executes external operations whose effects depend on test configuration and scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_test_suite Rate-limited

run_test_suite 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": {
    "run_test_suite": {
      "limits": [
        {
          "counter": "run_test_suite_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 Omise MCP Server, so you can run agents against it safely.

FAQ

Questions about run_test_suite

What does the run_test_suite tool do? +

Run comprehensive test suite. It is categorised as a Execute tool in the Omise 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 run_test_suite? +

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

What risk level is run_test_suite? +

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

Can I rate-limit run_test_suite? +

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

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

run_test_suite is provided by the Omise MCP Server MCP server (jun-omise/omise-mcp-alpha). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.