Map hosted OAuth consent to command permission classes

Open
#1,907 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Read the design and task 6.6 linked from the issue, then inspect the existing skill consent checkboxes and the command permission checks they feed. Add a test for each grant, confirming API Read allows read commands and the read execute tool, while API Write allows write and destructive commands. The issue is done when both grant behaviors are covered by tests.

Written by the indexing model from the issue text.

Description

enhancement MCP

Part of #1357. Plan: cli-first-mcp task 6.6 (design, tasks). Depends on #1880, #1899.

Keep #1670's API Read and API Write grants: Read allows read commands (and the read execute tool), Write allows write and destructive commands. The existing skill checkboxes map to command groups until consent is simplified.

Related: #941, #816.

Done when

  • A test per grant.

via @BYK.

--

View Session in Sentry

Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.