T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:33- Finding
Excessive Tool Permissions and Activation Scope
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mainly a read-only Azure inventory helper, but it asks for unnecessary write authority and contains broad, conflicting instructions that should be reviewed before installation.
Install only if you are comfortable with a command-capable skill using your local Azure CLI login. Treat it as needing review: remove or deny write access if possible, keep use limited to explicit read-only Azure inventory or health-check questions, and prefer commands that pass --subscription directly instead of changing the saved Azure CLI default subscription.
SKILL.md:33Excessive Tool Permissions and Activation Scope
SKILL.md:86Read-Only Guarantee Contradicted by Persistent Azure CLI Context Modification
The skill claims all operations are read-only, yet its declared tools include write capability. In an agent setting, tool declarations often determine what the runtime may permit, so this mismatch can enable state-changing behavior despite the natural-language policy saying otherwise.
A trigger condition that activates for generic Operations-related tasks is too broad for a skill that can execute commands. Over-broad activation increases the chance the agent routes unrelated requests into this skill, where command execution and Azure-context actions may occur without sufficiently specific user intent.
The skill repeatedly states that the free version excludes security auditing, but later content claims it provides automated security audit functionality. This inconsistency can mislead the agent or user about the skill’s actual scope and may cause it to be invoked for sensitive security-review tasks it was not meant or validated to perform.
The manifest describes a narrowly scoped, read-only Azure query skill, but later sections advertise generic file processing, external API integration, and command execution. This broadens the apparent authority of the skill beyond its declared purpose, increasing the chance of unsafe invocation, unexpected data handling, or misuse of available tools.
The invocation guidance is directionally correct but lacks a concrete bounded trigger list and negative examples. That ambiguity makes accidental overuse more likely, especially because the file elsewhere contains inconsistent claims about broader capabilities.
No suspicious patterns detected.