set_test_case_automated · Tuskr MCP: Risk & Policy

WHAT IT DOES

What set_test_case_automated does on Tuskr

AI agents use set_test_case_automated 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_case_automated needs a policy

This tool creates or modifies data reversibly by updating a boolean field on an existing test case. It is a Write action (update operation) rather than Read (no data retrieval), Execute (no command/code execution), Destructive (the change is reversible by setting the field to a different value), or Financial.

From the tool's definition The tool description states it "Set[s] the custom Tuskr field `automated` on an existing case", which modifies an existing test case record by updating a field value.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_test_case_automated Rate-limited

set_test_case_automated 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_case_automated": {
      "limits": [
        {
          "counter": "set_test_case_automated_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_case_automated

What does the set_test_case_automated tool do? +

Set the custom Tuskr field automated on an existing case (true or false). 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_case_automated? +

Register the Tuskr MCP server in PolicyLayer and add a rule for set_test_case_automated: 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_case_automated? +

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

Can I rate-limit set_test_case_automated? +

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

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

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