Undeclared Tool Scope
- Category
- MCP Least Privilege
- Confidence
- 70% confidence
- Finding
Without declared permissions the skill's intent is opaque and cannot be validated.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a planning-analysis helper with an optional local PDDL parser, and I did not find hidden persistence, credential access, network execution, or destructive behavior.
Install only if you want an advisory planning framework for complex multi-actor tasks. Treat its formal PDDL difficulty score as a rough heuristic, not a precise implementation of the thesis metric, and review outputs before applying them to sensitive operational plans.
Without declared permissions the skill's intent is opaque and cannot be validated.
The invocation guidance is broad enough to capture generic planning, analysis, and problem-solving requests, which can cause the skill to trigger outside its intended niche. Over-broad auto-invocation increases the chance the agent applies this methodology to sensitive operational, migration, or decision-support tasks without clear user intent, potentially shaping outputs inappropriately or exposing adjacent capabilities.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# Types
types_node = find_section(self.domain, ':types')
if types_node:
# Simplistic type parsing (a b - parent)
current_objs = []
for token in types_node[1:]:
if token == '-':
The docstring at L208-L210 claims the method uses a difficulty metric based on agents multiplied by entanglement and defines entanglement in terms of shared static resources. The actual code at L212-L225 never computes entanglement or such a product; it only derives a ratio of agent instances to total objects and labels complexity from agent-count cutoffs.
No suspicious patterns detected.