anti-rogue-actions

Enforce API guardrails and validate permissions and bounds using PowerShell scripts.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/coff33ninja/ai-skills-mcp --skill anti-rogue-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-rogue-actions
Source: https://github.com/coff33ninja/ai-skills-mcp/tree/main/skills/anti-rogue-actions
Command: npx skills add https://github.com/coff33ninja/ai-skills-mcp --skill anti-rogue-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires powershell, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents unauthorized, destructive, or nonsensical actions from being performed via API calls, reducing production agent failures.

Core Features & Use Cases

  • Pre-execution Sanity Checks: Ensures destructive operations are validated for permissions, bounds, and safety.
  • Bounds Enforcement: Ensures quantity, depth, scope, and limit parameters are set.
  • Dry-run Verification: Allows verification of operations before execution.
  • Scope Narrowing: Restricts operations to the smallest possible scope.
  • Confirmation for Destructive Chains: Confirms each step of a destructive chain.

Quick Start

Copy the 'sanity-check.ps1' script to your project's .ai_scripts/ directory and run it with -Command and -MaxItems flags to check for destructive commands and target size.

Frequently Asked Questions about anti-rogue-actions

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

FAQPage Schema
How do I prevent destructive API calls from executing without validation?

Prevent destructive API calls by enforcing pre-execution sanity checks that validate permissions, parameter bounds, and business logic guardrails before operations run, stopping unauthorized or nonsensical actions in production environments.

What are pre-execution sanity checks for API business logic?

Pre-execution sanity checks are validation steps that enforce permission boundaries, parameter bounds, and scope narrowing before an API call executes, ensuring destructive operations require explicit confirmation and target the smallest possible scope.

Do I need PowerShell to run pre-execution validation scripts for APIs?

Yes, you need PowerShell installed to execute the validation scripts. You copy the sanity-check script to your project's .ai_scripts directory and run it with command and target size flags to validate operations.

Can I dry-run API operations to verify safety before execution?

Yes, dry-run verification allows you to check operations for destructive commands and target size before actual execution. Running the sanity-check script validates parameter limits and scope without committing changes.

How do I enforce parameter bounds and scope limits on API requests?

Enforce parameter bounds by ensuring quantity, depth, scope, and limit parameters are explicitly set and validated before execution. Scope narrowing restricts operations to the smallest possible target area to prevent runaway actions.

What is the best way to confirm destructive API operation chains?

The best way to confirm destructive chains is to validate each step individually, enforcing business logic guardrails and permission boundaries at every stage, requiring explicit confirmation before proceeding to the next destructive action.