testmo_update_folder · Testmo MCP: Risk & Policy

WHAT IT DOES

What testmo_update_folder does on Testmo

AI agents use testmo_update_folder 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_update_folder needs a policy

The tool appears to modify folder metadata or properties within a test management system. This is a Write operation because updates are typically reversible (you can update again). Without a detailed description, confidence is moderated, but the 'update' verb and context of a test management system where folders are logical containers suggest reversible data modification rather than deletion or code execution.

From the tool's definition Tool name 'testmo_update_folder' indicates modification of folder data. The description is empty, but sibling tools include 'testmo_batch_update_cases', 'testmo_batch_create_cases', and other Write operations that modify Testmo resources, establishing a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testmo_update_folder Rate-limited

testmo_update_folder 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_update_folder": {
      "limits": [
        {
          "counter": "testmo_update_folder_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_update_folder

What does the testmo_update_folder tool do? +

testmo_update_folder. 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_update_folder? +

Register the Testmo MCP server in PolicyLayer and add a rule for testmo_update_folder: 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_update_folder? +

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

Can I rate-limit testmo_update_folder? +

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

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

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