AI agents use import_behave_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 modifies the test management system by ingesting and storing test results. It is Write rather than Read (data is being created/persisted), not Execute (it doesn't run external commands—it imports pre-computed results), not Destructive (results can be re-imported or updated), and not Financial.
From the tool's definition Tool name 'import_behave_results' and description 'Import Behave JSON test results' indicate data creation/modification. The tool writes test execution results into Xray Test Management system, creating or updating test result records.
Attacks that exploit this kind of access
Import Behave 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_behave_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_behave_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_behave_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_behave_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_behave_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 →