testmo_complete_automation_run_thread

WHAT IT DOES

What testmo_complete_automation_run_thread does on Testmo

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

WHY IT NEEDS A POLICY

Why testmo_complete_automation_run_thread needs a policy

This operation updates a record's status/state reversibly (a completed thread could theoretically be reset or modified by other operations), making it a Write rather than Execute or Destructive action.

From the tool's definition Tool name contains 'complete' and description states 'Mark an automation run thread as completed' — this modifies the state of an existing automation run thread, changing its status from active to completed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testmo_complete_automation_run_thread Rate-limited

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

FAQ

Questions about testmo_complete_automation_run_thread

What does the testmo_complete_automation_run_thread tool do? +

Mark an automation run thread as completed. It is categorised as a Write tool in the Testmo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on testmo_complete_automation_run_thread? +

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

What risk level is testmo_complete_automation_run_thread? +

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

Can I rate-limit testmo_complete_automation_run_thread? +

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

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

testmo_complete_automation_run_thread is provided by the Testmo MCP server (strelec00/testmo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.