ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 5/5

permission-creep-scanner

Helps detect permission creep in AI agent skills — flags when a skill's actual code accesses resources far beyond what its declared purpose requires, like a "fix typo" skill reading your .env file.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/andyxinweiminicloud/permission-creep-scanner
Or

What This Skill Does

The permission-creep-scanner is a crucial security utility for the OpenClaw ecosystem. It acts as a static analysis agent that audits other AI skills to identify discrepancies between their stated mission and their actual code behavior. As AI agents gain more autonomy, they often interact with sensitive system files. This skill inspects incoming agent code to detect "permission creep"—where a simple tool, like a text formatter, surreptitiously attempts to access sensitive directories such as .ssh or .aws, or initiates unauthorized network connections. By parsing the skill's metadata against its implementation, it provides a transparency report that helps you decide if a specific tool is trustworthy before granting it execution privileges.

Installation

You can integrate this security layer directly into your environment using the OpenClaw command-line interface. Run the following command in your terminal: clawhub install openclaw/skills/security/permission-creep-scanner Ensure your OpenClaw runtime is updated to the latest version to support the full depth of the scanner's heuristic engine.

Use Cases

This scanner is essential for developers and power users who regularly pull community-created skills. Use it when:

  • Auditing third-party skills before deployment in a sensitive production environment.
  • Reviewing open-source contributions to your custom AI agents.
  • Enforcing a "least privilege" policy across your agent fleet by identifying over-scoped dependencies.
  • Performing a security baseline check on automated workflows that touch your local filesystem or credentials.

Example Prompts

  1. "@permission-creep-scanner scan the latest repository at /local/downloads/auto-git-committer to see if it accesses any environment variables."
  2. "@permission-creep-scanner audit this code [pasted code] and report any high-severity mismatches regarding external network calls."
  3. "@permission-creep-scanner evaluate the provided Capsule JSON for potential data exfiltration risks before I execute it in my workspace."

Tips & Limitations

  • Static vs. Dynamic: This tool performs static analysis. It is highly effective at catching hardcoded paths and obvious escalation patterns, but it may struggle with highly obfuscated or dynamically loaded code.
  • Context Matters: Always verify the scanner's output; sometimes legitimate dependencies (like a logger) might look like "external-api" calls. Review the "Risk rating" provided to prioritize your investigation. The tool works best when provided with the full source code rather than just a URL.

Metadata

Stars4473
Views1
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-andyxinweiminicloud-permission-creep-scanner": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#security#audit#privacy#static-analysis#agent-safety
Safety Score: 5/5

Flags: file-read, code-execution