the updateTestCaseElement tool can update a specific element within a test case. Test case elements represent individual steps in a test case, such as interactions (clicks, text input) or assertions (checking if elements are visible, have text, etc.). Each element has selectors that identify the ...
AI agents use updateTestCaseElement to create or update resources in Octomind — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Octomind environment.
This tool modifies test case elements by updating locator lines (CSS selectors or other element identifiers used in automated testing). While it only allows updates to a specific field (locatorLine) and not deletions, it is a reversible write operation that changes test configuration data.
From the tool's definition Tool description states it "can update a specific element within a test case" and "You can only update the locatorLine of the element in question".
Documented attack patterns abuse exactly the kind of access updateTestCaseElement gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octomind, and nothing reaches the server without passing your rules. This is the rule we recommend for updateTestCaseElement:
{
"version": "1",
"default": "deny",
"tools": {
"updateTestCaseElement": {
"limits": [
{
"counter": "updatetestcaseelement_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}updateTestCaseElement 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.
Free to start. No card required.
the updateTestCaseElement tool can update a specific element within a test case. Test case elements represent individual steps in a test case, such as interactions (clicks, text input) or assertions (checking if elements are visible, have text, etc.). Each element has selectors that identify the target element on the page and an action to perform or assertion to verify. You can only update the locatorLine of the element in question, for everything else the user currently needs to use the octomind ui. It is categorised as a Write tool in the Octomind MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Octomind MCP server in PolicyLayer and add a rule for updateTestCaseElement: 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 Octomind. Nothing to install.
updateTestCaseElement 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 updateTestCaseElement 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 updateTestCaseElement. 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.
updateTestCaseElement is provided by the Octomind MCP server (octomind-dev/octomind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octomind, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Octomind tools catalogued and risk-classified — across an index of 43,000+ MCP servers.