Consent And Scoping

Organization

RedHatProductSecurity

consent-and-scoping

Enforce granular OAuth scopes and explicit user consent in MCP servers. Use when designing, building, or reviewing MCP server permission models, scope definitions, or consent flows.

Overview

Publisher	RedHatProductSecurity
Repository	`prodsec-skills`
Skill name	`consent-and-scoping`
Stars	56
Forks	9
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by RedHatProductSecurity on GitHub. Read the source before you install it.

Installation

Install the Consent And Scoping AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/consent-and-scoping
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/consent-and-scoping

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills.git /tmp/prodsec-skills
mkdir -p .claude/skills
cp -r /tmp/prodsec-skills/module/skills/consent-and-scoping .claude/skills/consent-and-scoping

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Consent And Scoping in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Consent And Scoping on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Consent And Scoping is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Consent and Granular Scoping for MCP Servers

Security Requirement

MCP servers MUST implement granular OAuth scopes and ensure users explicitly consent to them. Scopes should map to specific tool capabilities, not broad "access everything" permissions.

Granular Scope Design

Define scopes at the tool and action level:

Scope	Permission
`email.send`	Send emails via the email tool
`email.read`	Read emails via the email tool
`files.read`	Read files via the filesystem tool
`files.write`	Write files via the filesystem tool
`database.query`	Execute read-only database queries
`database.modify`	Execute write database operations

Avoid overly broad scopes like tools.all or admin that grant blanket access.

Explicit Consent

Users MUST explicitly consent to the scopes being requested. The consent flow should:

Clearly describe what each scope allows
Let users see the specific tools and actions being authorized
Allow users to selectively grant or deny individual scopes
Record consent decisions for audit purposes

Confused Deputy Prevention

Granular scoping prevents confused deputy attacks where an MCP server is tricked into performing unauthorized actions:

A tool with email.read scope cannot be manipulated to send emails
A tool with files.read scope cannot be used to write or delete files
The scope boundary acts as a hard limit regardless of what the LLM requests

Implementation Checklist

Define granular scopes for each tool and action (e.g., email.send, files.read)
Publish scopes in Protected Resource Metadata (scopes_supported)
Enforce scope checks on every tool invocation
Implement user consent flow that clearly describes each scope
Allow users to selectively grant or deny scopes
Log consent decisions for audit
Reject tool invocations that exceed the granted scopes
Review and update scopes when new tools are added

Frequently asked questions

What does the Consent And Scoping AI skill do?

Enforce granular OAuth scopes and explicit user consent in MCP servers. Use when designing, building, or reviewing MCP server permission models, scope definitions, or consent flows.

Why use Consent And Scoping on TypingMind?

Because you install it once and use it with any model. Consent And Scoping is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Consent And Scoping in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/consent-and-scoping. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Consent And Scoping?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Consent And Scoping?

As many as you like. As long as a model supports skills, you can use Consent And Scoping with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Consent And Scoping AI skill free?

Yes. It is published on GitHub by RedHatProductSecurity under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gog

openclaw

OrganizationPopular

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Healthcheck

Audit/harden OpenClaw hosts: SSH, firewall, updates, exposure, backups, disk encryption, gateway security.

Change Impact

Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths,…

Test Collaboration

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Consent and Granular Scoping for MCP Servers

Security Requirement

Granular Scope Design

Explicit Consent

Confused Deputy Prevention

Implementation Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now