jira-bug-query Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

jira-bug-query is an AI agent skill. ClawSecure audited jira-bug-query across 2 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 Unauthorized Tool Use, Permissions Manifest and Policy Violation, including Undeclared Network Access and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is jira-bug-query safe?

ClawSecure audited jira-bug-query and assigned a security score of 90/100 (Safe), identifying 3 findings across Unauthorized Tool Use and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in jira-bug-query?

ClawSecure identified 3 findings in jira-bug-query, concentrated in Unauthorized Tool Use, Permissions Manifest and Policy Violation. The most severe include Undeclared Network Access and Missing config.json - agent may not be properly configured.

How was jira-bug-query audited?

ClawSecure ran jira-bug-query through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 2 files.

What does a score of 90 mean?

ClawSecure assigned jira-bug-query 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 jira-bug-query

ClawSecure detected 3 security findings in jira-bug-query, spanning Unauthorized Tool Use, Permissions Manifest and Policy Violation.

medium · Undeclared Network Access. Unauthorized Tool Use finding detected in SKILL.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
info · Missing License Declaration. Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for jira-bug-query

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

jira-bug-query 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

How to Secure an MCP Server: The 2026 Guide→What Is MCP Security? Model Context Protocol Explained→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

activity_sprint_assessScore 80/100 activity_sprint_assessScore 80/100 wordpress-proScore 95/100 jina-readerScore 95/100 feishu-whiteboardScore 95/100

Scanned on June 12, 2026. jira-bug-query 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