AI agents use update_case to create or update resources in QASE MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QASE MCP Server environment.
The tool creates or modifies data (a test case) in a reversible manner. It does not delete, execute code, move money, or trigger external operations. Updates to test case metadata, descriptions, or configurations are typical Write operations.
From the tool's definition Tool name is 'update_case' and description states 'Update an existing test case' — this modifies an existing resource in the Qase test management system.
Documented attack patterns abuse exactly the kind of access update_case gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QASE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_case:
{
"version": "1",
"default": "deny",
"tools": {
"update_case": {
"limits": [
{
"counter": "update_case_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_case 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 an existing test case. It is categorised as a Write tool in the QASE MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QASE MCP Server MCP server in PolicyLayer and add a rule for update_case: 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 QASE MCP Server. Nothing to install.
update_case 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 update_case 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 update_case. 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.
update_case is provided by the QASE MCP Server MCP server (rikuson/mcp-qase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QASE 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.
26 QASE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.