create_status · Zephyr Scale MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_status does on Zephyr Scale MCP Server

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

The 'create_' prefix strongly indicates a write operation that creates new test status entities within Zephyr Scale's test management system. While the empty description reduces confidence slightly, the consistent pattern of create_* tools on this server and the nature of test management systems (where status creation is a reversible configuration operation) suggests this is a Write rather than Execute or…

From the tool's definition Tool name 'create_status' indicates data creation. Context shows other sibling tools all use 'create_' prefix for write operations (create_environment, create_folder, create_priority, create_test_case, create_test_cycle, create_test_execution).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_status Rate-limited

create_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": {
    "create_status": {
      "limits": [
        {
          "counter": "create_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 create_status

What does the create_status tool do? +

create_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 create_status? +

Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for create_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 create_status? +

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

Can I rate-limit create_status? +

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

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

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