update_gherkin_test_definition · Mxray MCP: Risk & Policy

WHAT IT DOES

What update_gherkin_test_definition does on Mxray

AI agents use update_gherkin_test_definition 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 update_gherkin_test_definition needs a policy

This tool creates or modifies test definitions reversibly via a GraphQL API. It falls into the Write category as it updates existing test data without being irreversible (Destructive) or executing arbitrary code (Execute). Severity is medium because unintended modifications to test definitions could corrupt test suites and impact CI/CD pipelines, but the effect is bounded to test metadata and reversible.

From the tool's definition Tool name uses 'update' verb and description states 'Update the Gherkin scenario definition' — explicitly modifies test data. Changes are reversible (can update again to previous state).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_gherkin_test_definition Rate-limited

update_gherkin_test_definition 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": {
    "update_gherkin_test_definition": {
      "limits": [
        {
          "counter": "update_gherkin_test_definition_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 update_gherkin_test_definition

What does the update_gherkin_test_definition tool do? +

Update the Gherkin scenario definition of a Cucumber test via GraphQL (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 update_gherkin_test_definition? +

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

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

Can I rate-limit update_gherkin_test_definition? +

Yes. Add a rate_limit block to the update_gherkin_test_definition 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 update_gherkin_test_definition completely? +

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

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