create_manual_test_suite · Testdino MCP: Risk & Policy

WHAT IT DOES

What create_manual_test_suite does on Testdino

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

WHY IT NEEDS A POLICY

Why create_manual_test_suite needs a policy

An AI agent can call create_manual_test_suite faster than any human can review — one bad instruction and it creates or modifies resources in Testdino by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_manual_test_suite Rate-limited

create_manual_test_suite 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_manual_test_suite": {
      "limits": [
        {
          "counter": "create_manual_test_suite_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 Testdino, so you can run agents against it safely.

FAQ

Questions about create_manual_test_suite

What does the create_manual_test_suite tool do? +

Create a new test suite folder to organize test cases. Use this to create a logical grouping for related test cases. Suites can be nested by providing a parentSuiteId. It is categorised as a Write tool in the Testdino 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_manual_test_suite? +

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

What risk level is create_manual_test_suite? +

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

Can I rate-limit create_manual_test_suite? +

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

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

create_manual_test_suite is provided by the Testdino MCP server (testdino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.