sc4sap:trust-session

Pre-grant SAP MCP permissions for the active session.

46|15|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/babamba2/superclaude-for-sap --skill sc4sap-trust-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sc4sap:trust-session
Source: https://github.com/babamba2/superclaude-for-sap/tree/main/skills/trust-session
Command: npx skills add https://github.com/babamba2/superclaude-for-sap --skill sc4sap-trust-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internal permission bootstrap that pre-grants the necessary SAP MCP tool permissions for the current session, eliminating prompts during automated SAP pipelines and ensuring seamless program execution.

Core Features & Use Cases

  • Pre-grants SAP MCP permissions for the active session, scoped to SAP MCP handlers and the legacy ABAP ADT namespace, excluding sensitive data access tools like GetTableContents and GetSqlQuery.
  • Enforces downstream Agent dispatch mode to bypass prompts and maintain deterministic automation.
  • Manages runtime state I/O under .sc4sap (e.g., session-trust.log, state.json) for auditability, while restricting writes outside the scoped directory.
  • Requires invocation by a parent skill; standalone use is refused to maintain security boundaries.

Quick Start

Invoke this only from a parent skill to grant session-wide MCP permissions before the first Create*/Update* MCP call.

Frequently Asked Questions about sc4sap:trust-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-approve SAP MCP permissions for ABAP automation pipelines?▼

Auto-approving SAP MCP permissions requires a session-scoped bootstrap that pre-grants access to SAP MCP handlers and the ABAP ADT namespace, eliminating interactive prompts during automated pipeline execution.

What is session-scoped permission bootstrap for SAP MCP tasks?▼

Session-scoped permission bootstrap is a mechanism that pre-grants SAP MCP tool permissions for the active session, ensuring seamless automated program execution while preserving explicit prompts for sensitive non-SAP tools.

Can I use this SAP session trust bootstrap as a standalone skill?▼

You cannot use this SAP session trust bootstrap as a standalone skill. It requires invocation by a parent skill that orchestrates ABAP tasks, and standalone use is refused to maintain security boundaries.

Does the SAP MCP permission bootstrap restrict sensitive data access?▼

Yes, the SAP MCP permission bootstrap restricts sensitive data access by excluding tools like GetTableContents and GetSqlQuery from auto-approval, while enforcing explicit permission prompts for non-SAP tools.

How do I audit SAP MCP permission activations during an automation session?▼

To audit SAP MCP permission activations, the bootstrap manages runtime state I/O under the .sc4sap directory, writing to files like session-trust.log and state.json to ensure full auditability of all session actions.

What are the limitations of bypassing prompts in SAP MCP automated pipelines?▼

Limitations of bypassing SAP MCP prompts include restricting file writes to the scoped .sc4sap directory and excluding sensitive data access tools, ensuring automation does not compromise non-SAP tool security boundaries.