複数のテストケースを一括で作成します
AI agents use create_test_cases_in_bulk 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.
This tool creates new test cases, which is a reversible write operation with no destructive intent. It modifies the Qase project by adding new data. The severity is medium because bulk creation could impact test management workflows and create many artifacts that require cleanup, but the operation is reversible (test cases can be deleted).
From the tool's definition Tool name 'create_test_cases_in_bulk' and description indicate creation of multiple test cases at once. The Japanese description '複数のテストケースを一括で作成します' translates to 'Create multiple test cases in bulk.' This is a write operation that creates data in the Qase…
Attacks that exploit this kind of access
複数のテストケースを一括で作成します. 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 create_test_cases_in_bulk: 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.
create_test_cases_in_bulk 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 create_test_cases_in_bulk 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 create_test_cases_in_bulk. 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.
create_test_cases_in_bulk is provided by the Qase MCP Server MCP server (rayyokoyama/qase-mcp-server). 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 →