update_test · Mxray MCP: Risk & Policy

WHAT IT DOES

What update_test does on Mxray

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

This tool modifies existing test records in Jira reversibly without deleting data or executing arbitrary operations. It is a Write operation with medium severity because unintended modifications to test definitions could disrupt testing workflows and project integrity, though changes are typically reversible via additional updates or version history.

From the tool's definition Tool name 'update_test' and description 'Update fields of an existing test in Jira' directly indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_test Rate-limited

update_test 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_test": {
      "limits": [
        {
          "counter": "update_test_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_test

What does the update_test tool do? +

Update fields of an existing test in Jira. 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_test? +

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

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

Can I rate-limit update_test? +

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

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

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