import_feature_file · Mxray MCP: Risk & Policy

WHAT IT DOES

What import_feature_file does on Mxray

AI agents use import_feature_file 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.

WHY IT NEEDS A POLICY

Why import_feature_file needs a policy

This tool creates or updates tests in Xray, which are data entities that can be modified reversibly. While 'import' might suggest a read operation, the description explicitly states it will 'create/update tests', making it a Write operation. Severity is medium because it modifies test management data (not production data or financial systems), but the blast radius is limited to test artifacts.

From the tool's definition Tool description states 'Import a Cucumber .feature file to create/update tests in Xray', indicating it creates or modifies test data in Xray through file import.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_feature_file Rate-limited

import_feature_file 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_feature_file": {
      "limits": [
        {
          "counter": "import_feature_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mxray, so you can run agents against it safely.

FAQ

Questions about import_feature_file

What does the import_feature_file tool do? +

Import a Cucumber .feature file to create/update tests in Xray (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.

How do I enforce a policy on import_feature_file? +

Register the Mxray MCP server in PolicyLayer and add a rule for import_feature_file: 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.

What risk level is import_feature_file? +

import_feature_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_feature_file? +

Yes. Add a rate_limit block to the import_feature_file 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.

How do I block import_feature_file completely? +

Set action: deny in the PolicyLayer policy for import_feature_file. 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.

What MCP server provides import_feature_file? +

import_feature_file 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.