AI agents use create_test_set to create or update resources in Mxray — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mxray environment.
This tool creates a new test set, which is a reversible write operation. It adds data to the Jira Cloud system but does not execute arbitrary code, delete data irreversibly, or move financial resources. The severity is medium because creating test sets in a test management system could affect test execution workflows, but the impact is limited to test metadata and is easily reversible.
From the tool's definition Tool name is 'create_test_set' and description states 'Create a new test set in Jira.' The verb 'create' and 'new' indicate data creation.
Attacks that exploit this kind of access
Create a new test set in Jira. It is categorised as a Write tool in the Mxray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mxray MCP server in PolicyLayer and add a rule for create_test_set: 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 Mxray. Nothing to install.
create_test_set 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_set 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_set. 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_set is provided by the Mxray MCP server (mxray-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 →