write_test_cases · Targetprocess MCP: Risk & Policy

WHAT IT DOES

What write_test_cases does on Targetprocess

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

WHY IT NEEDS A POLICY

Why write_test_cases needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_test_cases Rate-limited

write_test_cases 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": {
    "write_test_cases": {
      "limits": [
        {
          "counter": "write_test_cases_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 Targetprocess, so you can run agents against it safely.

FAQ

Questions about write_test_cases

What does the write_test_cases tool do? +

<step action>. It is categorised as a Write tool in the Targetprocess MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on write_test_cases? +

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

What risk level is write_test_cases? +

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

Can I rate-limit write_test_cases? +

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

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

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