AI agents use testmo_create_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.
Creating a folder is a reversible write operation that organizes test cases within a project. It does not execute code, delete data irreversibly, or move money. The blast radius is minimal—worst case, an unwanted folder can be deleted. This is a standard Write category operation.
From the tool's definition Tool name 'testmo_create_folder' and description 'Create a new folder in a Testmo project' indicate a creation action that adds new organizational structure to the test management system.
Attacks that exploit this kind of access
Create a new folder in a Testmo project. 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.
Register the Testmo MCP server in PolicyLayer and add a rule for testmo_create_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.
testmo_create_folder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the testmo_create_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.
Set action: deny in the PolicyLayer policy for testmo_create_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.
testmo_create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →