AI agents use import_cucumber_results 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 writes/creates test result data into Xray test management system by importing Cucumber test results. While the operation creates new records rather than updating existing ones, it is fundamentally a write operation that modifies the state of the test management system.
From the tool's definition Tool name is 'import_cucumber_results' and description states it 'Import[s] Cucumber JSON test results'. The verb 'import' indicates data creation or modification of test result records in Xray, which is a reversible write operation.
Attacks that exploit this kind of access
Import Cucumber JSON test results (requires Xray credentials). 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 import_cucumber_results: 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.
import_cucumber_results 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 import_cucumber_results 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 import_cucumber_results. 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.
import_cucumber_results 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 →