import_feature_file · Xray MCP: Risk & Policy

WHAT IT DOES

What import_feature_file does on Xray MCP

AI agents use import_feature_file to create or update resources in Xray MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xray MCP environment.

WHY IT NEEDS A POLICY

Why import_feature_file needs a policy

The tool performs reversible creation and modification of test data (BDD tests) rather than deletion. While it can update existing tests, changes can be undone through subsequent imports or direct edits in Jira. This makes it Write rather than Destructive. It is not Execute because it does not run code or trigger external operations — it merely ingests and transforms a file format into test definitions.

From the tool's definition Tool description states it "Creates or updates BDD tests from Gherkin scenarios" — this is reversible modification of test data in Xray/Jira. The import operation modifies existing test artifacts or creates new ones.

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 Xray MCP, so you can run agents against it safely.

FAQ

Questions about import_feature_file

What does the import_feature_file tool do? +

Import Cucumber .feature file to Xray. Creates or updates BDD tests from Gherkin scenarios. It is categorised as a Write tool in the Xray MCP 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 Xray 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 Xray MCP. 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 Xray MCP server (korfu/mcp-xray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.