update_status · Zephyr Scale MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_status does on Zephyr Scale MCP Server

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

WHY IT NEEDS A POLICY

Why update_status needs a policy

This tool modifies existing status records in Zephyr Scale, which is reversible through subsequent updates. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or perform read-only queries (Read).

From the tool's definition Tool name is 'update_status' with description 'Update an existing status.' The verb 'update' indicates modification of existing data in a test management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_status Rate-limited

update_status 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_status": {
      "limits": [
        {
          "counter": "update_status_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 Zephyr Scale MCP Server, so you can run agents against it safely.

FAQ

Questions about update_status

What does the update_status tool do? +

Update an existing status. It is categorised as a Write tool in the Zephyr Scale MCP Server 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_status? +

Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for update_status: 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 Zephyr Scale MCP Server. Nothing to install.

What risk level is update_status? +

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

Can I rate-limit update_status? +

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

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

update_status is provided by the Zephyr Scale MCP Server MCP server (metquay/zephyr-scale-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.