# qmetry_update_issue

Update an existing QMetry issue by DefectId and/or entityKey. Parameters: - DefectId (number) *required*: ID of the defect/issue to be updated - entityKey (string): Entity Key of the defect/issue to be updated - issueType (number): Issue type ID (e.g. Bug, Enhancement, etc.) - issuePriority (number): Issue priority ID (e.g. High, Medium, Low, etc.) - summary (string): Summary or title of the defect/issue - description (string): Detailed description of the defect/issue - issueOwner (number): Owner/user ID for the issue - affectedRelease (number): Release IDs affected by this issue - affectedCycles (number): Cycle IDs affected by this issue Output Description: JSON object with update status and details. Use Cases: 1. Update issue summary (title) 2. Change issue priority, type, or owner 3. Update affected release or cycles 4. Update description or environment 5. Bulk update using DefectId and/or entityKey Examples: 1. Update issue summary json { "DefectId": 118150, "summary": "Money withdrawal is success even if insufficient amount_updated" } Expected Output: Issue summary updated successfully. 2. Update issue priority json { "DefectId": 118150, "issuePriority": 189340 } Expected Output: Issue priority updated successfully. 3. Update issue type json { "DefectId": 118150, "issueType": 189337 } Expected Output: Issue type updated successfully. 4. Update affected release json { "DefectId": 118150, "affectedRelease": 3730 } Expected Output: Affected release updated successfully. Hints: 1. To get the DefectId, call the Issue/Fetch issue tool and use data[<index>].id from the response. 2. if you have pass issue key (VT-IS-5, MAC-IS-10 etc.) then first fetch issue by issue key to get issue id. 3. Along with DefectId, pass only those fields which are to be updated. 4. Refer to the Create Issue tool for valid field mappings and values. 5. You can update summary, priority, type, affectedRelease, affectedCycles, description, sync_with, issueOwner, component, environment, tcRunID, etc. 6. If you provide entityKey, it will be used for additional validation but DefectId is required.

Agent View of the PolicyLayer registry record for `qmetry_update_issue`. HTML page: https://policylayer.com/tools/smartbear-mcp/qmetry-update-issue

## Facts

- Tool: `qmetry_update_issue`
- Server: SmartBear MCP (`SmartBear/smartbear-mcp`) — https://policylayer.com/tools/smartbear-mcp.md
- Homepage: https://github.com/SmartBear/smartbear-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 9 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `summary` | string | no | Summary or title of the defect/issue |
| `DefectId` | number | yes | ID of the defect/issue to be updated |
| `entityKey` | string | no | Entity Key of the defect/issue to be updated |
| `issueType` | number | no | Issue type ID (e.g. Bug, Enhancement, etc.) |
| `issueOwner` | number | no | Owner/user ID for the issue |
| `description` | string | no | Detailed description of the defect/issue |
| `issuePriority` | number | no | Issue priority ID (e.g. High, Medium, Low, etc.) |
| `affectedCycles` | number | no | Cycle IDs affected by this issue |
| `affectedRelease` | number | no | Release IDs affected by this issue |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "qmetry_update_issue",
    "arguments": {
      "DefectId": 0
    }
  }
}
```

## Why qmetry_update_issue is rated Medium

This is a Write operation—it modifies existing data in the QMetry issue tracking system. The change is reversible since issue updates can be undone through subsequent updates. It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).

From the tool's own definition: "Tool performs 'Update an existing QMetry issue' with parameters for modifying issueType, issuePriority, summary, description, issueOwner, and affectedRelease fields."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches SmartBear MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "qmetry_update_issue": {
      "limits": [
        {
          "counter": "qmetry_update_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on SmartBear MCP (239)

- `collaborator_delete_collaborator_remote_system_configuration` — Destructive — https://policylayer.com/tools/smartbear-mcp/collaborator-delete-collaborator-remote-system-configuration.md
- `contract-testing_admin_delete_role` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-delete-role.md
- `contract-testing_admin_delete_team` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-delete-team.md
- `contract-testing_admin_delete_user` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-delete-user.md
- `contract-testing_admin_remove_role_from_user` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-remove-role-from-user.md
- `contract-testing_admin_remove_user_from_team` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-remove-user-from-team.md
- `contract-testing_admin_reset_roles` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-reset-roles.md
- `contract-testing_delete_all_integrations` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-all-integrations.md
- `contract-testing_delete_branch` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-branch.md
- `contract-testing_delete_environment` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-environment.md
- `contract-testing_delete_integration` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-integration.md
- `contract-testing_delete_pacticipant` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-pacticipant.md
- `contract-testing_delete_secret` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-secret.md
- `contract-testing_delete_webhook` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-webhook.md
- `contract-testing_regenerate_api_token` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-regenerate-api-token.md
- `contract-testing_remove_label_from_pacticipant` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-remove-label-from-pacticipant.md
- `reflect_cancel_suite_execution` — Destructive — https://policylayer.com/tools/smartbear-mcp/reflect-cancel-suite-execution.md
- `reflect_delete_previous_step` — Destructive — https://policylayer.com/tools/smartbear-mcp/reflect-delete-previous-step.md
- `swagger_delete_portal_product` — Destructive — https://policylayer.com/tools/smartbear-mcp/swagger-delete-portal-product.md
- `swagger_delete_table_of_contents` — Destructive — https://policylayer.com/tools/smartbear-mcp/swagger-delete-table-of-contents.md
- `collaborator_reviewservice_action` — Execute — https://policylayer.com/tools/smartbear-mcp/collaborator-reviewservice-action.md
- `collaborator_test_collaborator_remote_system_configuration_connection` — Execute — https://policylayer.com/tools/smartbear-mcp/collaborator-test-collaborator-remote-system-configuration-connection.md
- `contract-testing_execute_webhook` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-execute-webhook.md
- `contract-testing_generate_pact_tests` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-generate-pact-tests.md
- `contract-testing_review_pact_tests` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-review-pact-tests.md
- `contract-testing_test_execute_webhooks` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-test-execute-webhooks.md
- `reflect_add_prompt_step` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-add-prompt-step.md
- `reflect_connect_to_session` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-connect-to-session.md
- `reflect_execute_suite` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-execute-suite.md
- `reflect_run_test` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-run-test.md
- …and 209 more: https://policylayer.com/tools/smartbear-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=smartbear-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/smartbear-mcp