Update requirement (/api/v2/{project_id}/requirements/{id})
AI agents use requirements_update to create or update resources in Testomatio MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Testomatio MCP Server environment.
This tool creates or modifies data reversibly—it updates an existing requirement in the test management system. Changes can typically be reverted by subsequent updates. It is not destructive (data remains retrievable), not financial, and not Execute (no arbitrary code/command execution). Classification as Write is appropriate for reversible data modifications.
From the tool's definition Tool name contains 'update' and description indicates it modifies a requirement resource via PATCH/PUT operation (/api/v2/{project_id}/requirements/{id})
Documented attack patterns abuse exactly the kind of access requirements_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Testomatio MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for requirements_update:
{
"version": "1",
"default": "deny",
"tools": {
"requirements_update": {
"limits": [
{
"counter": "requirements_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}requirements_update 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.
Update requirement (/api/v2/{project_id}/requirements/{id}). It is categorised as a Write tool in the Testomatio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Testomatio MCP Server MCP server in PolicyLayer and add a rule for requirements_update: 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 Testomatio MCP Server. Nothing to install.
requirements_update 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 requirements_update 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 requirements_update. 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.
requirements_update is provided by the Testomatio MCP Server MCP server (testomatio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Testomatio MCP Server, 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.
10 Testomatio MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.