create_result_bulk

THE RISK

Medium Risk

Why create_result_bulk needs a policy

This tool creates test run results, which are new data records in the Qase platform. Creation is a reversible write operation (results can typically be edited or deleted).

From the tool's definition Tool name 'create_result_bulk' and description 'Create multiple test run results in bulk' indicate creation of multiple data records in the test management system.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access create_result_bulk gives an agent:

POLICY

How to control create_result_bulk

PolicyLayer is an MCP gateway — it sits between your AI agents and QASE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_result_bulk:

policy.json

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

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

Create a free account and register QASE MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More QASE MCP Server tools

Write create_case Create a new test case Write create_plan Create a new test plan Write create_project Create new project Write create_result Create test run result Write create_shared_step Create a new shared step Write create_suite Create a new test suite Write update_case Update an existing test case Write update_plan Update an existing test plan

All 26 QASE MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_result_bulk

What does the create_result_bulk tool do? +

Create multiple test run results in bulk. 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_result_bulk? +

Register the QASE MCP Server MCP server in PolicyLayer and add a rule for create_result_bulk: 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_result_bulk? +

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

Can I rate-limit create_result_bulk? +

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

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

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

Enforce policy on every QASE MCP Server tool call.

Start from QASE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →