iiRecord
Agentic AI Atlas · scope-boundary:tool-server-mcp-jira.scope
scope-boundary:tool-server-mcp-jira.scopea5c.ai
II.
ScopeBoundary JSON

scope-boundary:tool-server-mcp-jira.scope

Structured · live

scope-boundary:tool-server-mcp-jira.scope json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · sourceref-scope/scope-boundaries/tool-server-mcp-jira.yamlCluster · sourceref-scope
Record JSON
{
  "id": "scope-boundary:tool-server-mcp-jira.scope",
  "_kind": "ScopeBoundary",
  "_file": "sourceref-scope/scope-boundaries/tool-server-mcp-jira.yaml",
  "_cluster": "sourceref-scope",
  "attributes": {
    "subjectId": "tool-server:mcp-jira",
    "inScope": "Atlassian Jira issue / project access — search, transitions, comments, attachments.\n",
    "outOfScope": "Confluence content (separate MCP), Jira admin / scheme-management, and Atlassian-cloud billing.\n",
    "outOfScopeReasonIds": [
      "out-of-scope-reason:future-phase",
      "out-of-scope-reason:implementation-detail"
    ]
  },
  "outgoingEdges": [
    {
      "from": "scope-boundary:tool-server-mcp-jira.scope",
      "to": "tool-server:mcp-jira",
      "kind": "bounds_subject"
    },
    {
      "from": "scope-boundary:tool-server-mcp-jira.scope",
      "to": "out-of-scope-reason:future-phase",
      "kind": "has_out_of_scope_reason"
    },
    {
      "from": "scope-boundary:tool-server-mcp-jira.scope",
      "to": "out-of-scope-reason:implementation-detail",
      "kind": "has_out_of_scope_reason"
    }
  ],
  "incomingEdges": []
}