---

date: 2026-06-09 tags: [github, issue-types, mcp, agent-tooling] status: active graduated_to:

A native GitHub Issue Type is agent-applyable on create even though list_issue_types 403s

Symptom — mcp__github__list_issue_types returned 403 Resource not accessible by integration, so we assumed the agent couldn't use native Issue Types and designed the parked-problem flow to fall back to a label.

Root cause — the 403 is only on reading the org's type list; setting a type is a different, allowed path. Once the type exists in the org, issue_write with type: "Idea" applies it fine.

Fix — spike (temp issue #389, closed): created with type: Idea, then issue_read confirmed "issue_type":"Idea". The brainstorm parked-problem flow uses the native Idea type directly — no label fallback.

Guard — when a native Issue Type is wanted: the maintainer creates it once in the org UI (the agent can't), then the agent applies it via the type param on create. Don't read the list_issue_types 403 as "types are unusable". Distinct from 2026-06-08-issue-fields-not-board-fields-use-labels (that's about org fields; this is about types).