create_test_run · Qase MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_test_run does on Qase MCP Server

AI agents use create_test_run to create or update resources in Qase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qase MCP Server environment.

WHY IT NEEDS A POLICY

Why create_test_run needs a policy

The tool creates new test run entities within the Qase test management system. This is reversible (test runs can be deleted or archived) and has no destructive consequences. It falls squarely in the Write category—creating or modifying data without permanent loss.

From the tool's definition Tool name 'create_test_run' and description 'テスト実行を作成します' (creates a test run) indicate creation of new data. This modifies the test management system by adding a test run record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_test_run Rate-limited

create_test_run stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_test_run": {
      "limits": [
        {
          "counter": "create_test_run_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_test_run

What does the create_test_run tool do? +

テスト実行を作成します. It is categorised as a Write tool in the Qase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_test_run? +

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

What risk level is create_test_run? +

create_test_run is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_test_run? +

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

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

create_test_run is provided by the Qase MCP Server MCP server (rayyokoyama/qase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.