← Back to Scanner

sdicsc-email Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

sdicsc-email is an AI agent skill. ClawSecure audited sdicsc-email across 5 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 3 findings concentrate in Prompt Injection, Permissions Manifest and Policy Violation, including Prompt Injection Vector and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is sdicsc-email safe?

ClawSecure audited sdicsc-email and assigned a security score of 75/100 (Medium Risk), identifying 3 findings across Prompt Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in sdicsc-email?

ClawSecure identified 3 findings in sdicsc-email, concentrated in Prompt Injection, Permissions Manifest and Policy Violation. 1 was rated high or critical severity. The most severe include Prompt Injection Vector and Missing config.json - agent may not be properly configured.

How was sdicsc-email audited?

ClawSecure ran sdicsc-email through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 5 files.

What does a score of 75 mean?

ClawSecure assigned sdicsc-email a security score of 75/100, placing it in the Medium Risk range. This reflects 3 findings led by Prompt Injection that warrant review before production use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for sdicsc-email

ClawSecure detected 3 security findings in sdicsc-email, spanning Prompt Injection, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for sdicsc-email

Investigate prompt injection vectors
Prompt injection is one of the most critical threats to AI agents. Attackers can embed malicious instructions in content the agent processes, causing unintended actions. Review every point where sdicsc-email processes external content and add input validation and output filtering.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Resolve policy violations
sdicsc-email trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

The Sleeper Agent Problem: Why a Clean Scan Today Does Not Guarantee Safety TomorrowOWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

everything-claude-codeScore 90/100claude-code-openclawScore 85/100claude-code-openclawScore 85/100a2aScore 85/100a2aScore 85/100

Scanned on June 12, 2026. sdicsc-email is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan