← Back to Scanner

protom-bridge-email Security Audit Report

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

protom-bridge-email is an AI agent skill, created by boilerrat and published at openclaw/skills. ClawSecure audited protom-bridge-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 Policy Violation, Unauthorized Tool Use and Permissions Manifest, including Pattern detected: chmod 700 and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is protom-bridge-email safe?

ClawSecure audited protom-bridge-email and assigned a security score of 75/100 (Medium Risk), identifying 3 findings across Policy Violation and Unauthorized Tool Use. Review the findings below before installing.

What did ClawSecure find in protom-bridge-email?

ClawSecure identified 3 findings in protom-bridge-email, concentrated in Policy Violation, Unauthorized Tool Use and Permissions Manifest. 1 was rated high or critical severity. The most severe include Pattern detected: chmod 700 and Missing config.json - agent may not be properly configured.

How was protom-bridge-email audited?

ClawSecure ran protom-bridge-email through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 5 files from openclaw/skills.

What does a score of 75 mean?

ClawSecure assigned protom-bridge-email a security score of 75/100, placing it in the Medium Risk range. This reflects 3 findings led by Policy Violation 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 protom-bridge-email

ClawSecure detected 3 security findings in protom-bridge-email, spanning Policy Violation, Unauthorized Tool Use and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for protom-bridge-email

Resolve policy violations
protom-bridge-email trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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.
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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

context-modeScore 70/100kokoro-ttsScore 75/100agentpulseScore 80/100proactive-messagesScore 80/100agentpulseScore 80/100

Scanned on February 7, 2026. protom-bridge-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