← Back to Scanner

google-docs Security Audit Report

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

google-docs is an AI agent skill, created by byungkyu and published at openclaw/skills. ClawSecure audited google-docs across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 3 findings concentrate in Data Exfiltration, Permissions Manifest and Policy Violation, including Code block in SKILL.md at line 285 contains potentially… and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is google-docs safe?

ClawSecure audited google-docs and assigned a security score of 90/100 (Safe), identifying 3 findings across Data Exfiltration and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in google-docs?

ClawSecure identified 3 findings in google-docs, concentrated in Data Exfiltration, Permissions Manifest and Policy Violation. The most severe include Code block in SKILL.md at line 285 contains potentially… and Missing config.json - agent may not be properly configured.

How was google-docs audited?

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

What does a score of 90 mean?

ClawSecure assigned google-docs a security score of 90/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 3 findings detected are lower-severity. 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 google-docs

ClawSecure detected 3 security findings in google-docs, spanning Data Exfiltration, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for google-docs

Audit external network connections
google-docs sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.
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
google-docs 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

ClawHavoc Explained: The Malware Family Targeting AI Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

summarizeScore 95/100Powerpoint / PPTXScore 95/100cve-2026-42945-nginx-rewrite-analysisScore 85/100changelog-generatorScore 95/100md-to-docxScore 85/100

Scanned on March 2, 2026. google-docs 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