set_test_cases_automated_bulk · Tuskr MCP: Risk & Policy

WHAT IT DOES

What set_test_cases_automated_bulk does on Tuskr

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

WHY IT NEEDS A POLICY

Why set_test_cases_automated_bulk needs a policy

The tool modifies test case data by setting the `automated` field on multiple cases. This is a reversible write operation (the field can be changed again), not destructive deletion, not code execution, and not financial.

From the tool's definition Tool description explicitly states it 'Set `automated` on multiple cases' which modifies the `automated` field on test cases. The 'bulk' aspect and 'multiple cases' indicate scope of modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_test_cases_automated_bulk Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_test_cases_automated_bulk": {
      "limits": [
        {
          "counter": "set_test_cases_automated_bulk_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 Tuskr, so you can run agents against it safely.

FAQ

Questions about set_test_cases_automated_bulk

What does the set_test_cases_automated_bulk tool do? +

Set automated on multiple cases by key or id (automated field only). It is categorised as a Write tool in the Tuskr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_test_cases_automated_bulk? +

Register the Tuskr MCP server in PolicyLayer and add a rule for set_test_cases_automated_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 Tuskr. Nothing to install.

What risk level is set_test_cases_automated_bulk? +

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

Can I rate-limit set_test_cases_automated_bulk? +

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

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

set_test_cases_automated_bulk is provided by the Tuskr MCP server (zapkid/tuskr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.