skills.rest
hve4638
hve4638COMMUNITY
Explore all skills by this author →
GitHub

codex-call

Enforce pre-call validation for codex invocations with mandatory sandbox and approval-policy parameters.

Updated Mar 1, 2026
Search Tags:#workflow#security#validation#codex#mcp#governance
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill codex-call
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-call
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/common/skills/codex-call
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill codex-call

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unvalidated codex invocations by requiring explicit pre-checks before every mcp__codex__codex call.

Core Features & Use Cases

  • Enforces mandatory pre-call parameters (sandbox and approval-policy) for all codex invocations.
  • Applies across direct calls, cross-review workflows, ccg orchestration, and delegated subagents to ensure consistent governance.
  • Provides a clear, auditable guardrail for safe AI tool usage in automated pipelines.

Quick Start

Always include sandbox: 'danger-full-access' and approval-policy: 'never' when calling mcp__codex__codex.

Frequently Asked Questions about codex-call

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

FAQPage Schema
How do I validate codex calls before executing MCP tools?▼

To validate codex calls, enforce pre-call parameters by always including sandbox: 'danger-full-access' and approval-policy: 'never' when invoking mcp__codex__codex. This ensures consistent governance across direct calls and delegated workstreams.

Why do my automated codex invocations fail governance checks?▼

Automated codex invocations fail governance checks when they lack explicit pre-call validation. You must apply mandatory sandbox and approval-policy parameters to prevent ungoverned calls and ensure auditable guardrails in automated pipelines.

What is pre-call validation for MCP codex workflows?▼

Pre-call validation for MCP codex workflows is a governance mechanism that requires explicit parameter checks before every mcp__codex__codex call. It prevents unvalidated invocations across cross-review workflows and delegated subagents.

Do I need sandbox permissions to use codex in automated pipelines?▼

Yes, you need sandbox: 'danger-full-access' permissions to use codex in automated pipelines. This prerequisite, combined with approval-policy: 'never', enforces the required guardrails for safe AI tool usage.

Can I apply pre-call validation across cross-review workflows and subagents?▼

Yes, you can apply pre-call validation across cross-review workflows, ccg orchestration, and delegated subagents. This ensures consistent governance and constrains prompt usage according to policy across all execution paths.

What is the best way to prevent ungoverned codex calls in AI pipelines?▼

The best way to prevent ungoverned codex calls is to enforce mandatory pre-checks before every invocation. Requiring explicit sandbox and approval-policy parameters provides clear, auditable guardrails for safe AI tool usage in automated pipelines.

Related Skills

Explore More Software Engineering Skills→
ArvorCoArvorCo
96

constitution

Create or update a project constitution defining coding principles and governance rules.

Community
Advanced
HeadyAIHeadyAI
1

heady-audit-forge

Generate and preserve auditable evidence for regulatory compliance and external audits.

Official
Advanced
lorrandavidlorrandavid

code-review

Coordinate parallel code-review subagents and correlate findings into a prioritized report.

Community
Intermediate
leolionartleolionart
1

mcp-to-cli

Convert MCP definitions into standalone CLIs using mcporter.

Community
Intermediate