openclaw-sec
AI Agent Security Suite - Real-time protection against prompt injection, command injection, SSRF, path traversal, secrets exposure, and content policy violations
[](https://agentverus.ai/skill/43056cfd-1ae2-4316-8a3a-6540d4d69f77)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/43056cfd-1ae2-4316-8a3a-6540d4d69f77/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"43056cfd-1ae2-4316-8a3a-6540d4d69f77","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/43056cfd-1ae2-4316-8a3a-6540d4d69f77/trustCategory Scores
Findings (20)
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
Base64-encoded string decodes to content containing suspicious keywords.
→ Remove base64-encoded content or replace with plaintext. Obfuscation raises security concerns.
The skill references a direct IP address which is classified as high risk.
→ Replace direct IP addresses with proper domain names. IP-based URLs bypass DNS-based security controls.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The skill relies on third-party AI providers or APIs, expanding the remote dependency surface for prompts, inputs, or generated artifacts.
→ Review which external services or providers the skill depends on, what data crosses that boundary, and whether the dependency is necessary for the intended workflow.
The skill relies on external documentation, specs, or README content as part of its workflow, which introduces an additional remote dependency and trust boundary.
→ Review which external services or providers the skill depends on, what data crosses that boundary, and whether the dependency is necessary for the intended workflow.
The skill performs or enables higher-risk operations but does not define explicit safety boundaries describing what it must not do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).
The skill references 9 external URLs and also discusses auth/API/payment workflows, which increases the chance that sensitive operations depend on many remote endpoints.
→ Minimize external dependencies to reduce supply chain risk.
Found federated auth flow pattern: "OAuth"
→ Treat OAuth, 2FA, and token-refresh guidance as authentication-sensitive workflows. Explain scope, storage, and refresh behavior clearly so agents do not handle more credential material than necessary.
The skill references a localhost or private-network service URL which is classified as medium risk.
→ Review localhost/private-network service references carefully. Local service URLs can expose internal apps, admin panels, or developer tooling to agent-driven workflows.
Found local service access pattern: "http://localhost:6379"
→ Treat localhost and loopback services as privileged local attack surfaces. Require explicit approval, constrain reachable ports, and avoid combining local access with session reuse or tunneling.
Found skill path discovery pattern: "{baseDir}"
→ Treat dynamic skill path resolution and installation-path discovery as local filesystem reconnaissance. Scope which paths may be read or executed from, and avoid broad path probing unless the user explicitly requested it.
Found ui state enumeration pattern: "Check result"
→ Treat DOM/accessibility snapshots and clickable-element inventories as sensitive page-state extraction. Be explicit about when UI enumeration is allowed, especially on authenticated or local-only apps.
Found external ai provider delegation pattern: "OpenAI API"
→ Treat external AI-provider calls as data egress. Make it explicit what prompts, files, or images are sent to third-party providers and require approval before forwarding sensitive content.
The skill references a direct IP address which is classified as low risk.
→ Replace direct IP addresses with proper domain names. IP-based URLs bypass DNS-based security controls.
The skill references an unknown external domain which is classified as low risk.
→ Verify that this external dependency is trustworthy and necessary.
The skill references an unknown external domain which is classified as low risk.
→ Verify that this external dependency is trustworthy and necessary.
Found local file access pattern: "file://"
→ Treat local file browsing as privileged access. Restrict it to explicit user-approved paths and avoid combining it with unrestricted browser/session reuse.