Security Audit

polygon-automation

github.com/ComposioHQ/awesome-claude-skills

AI SkillCommit 99e2a2951545

TRUSTED

Scanned 6 days ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

polygon-automation received a trust score of 95/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.

SkillShield's automated analysis identified 1 finding: 0 critical, 0 high, 1 medium, and 0 low severity. Key findings include Skill grants broad access to Rube MCP tools beyond stated purpose.

The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.

Last analyzed on February 17, 2026 (commit 99e2a295). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.

Layer Breakdown

Manifest Analysis

100%

Static Code Analysis

100%

Dependency Graph

100%

LLM Behavioral Safety

93%

Behavioral Risk Signals

Shell Execution

1 finding

Dynamic Code

1 finding

Excessive Permissions

1 finding

Security Findings1

Severity	Finding	Layer	Location
MEDIUM	Skill grants broad access to Rube MCP tools beyond stated purpose The skill's manifest declares a dependency on the `rube` MCP, and its description focuses on 'Polygon Automation'. However, the exposed `RUBE_MULTI_EXECUTE_TOOL` function allows specifying any `tool_slug`. If the `rube` MCP provides access to tools beyond just Polygon-related operations, an attacker could potentially inject a `tool_slug` to execute arbitrary tools available through `rube`. This could lead to actions outside the intended scope of Polygon automation, such as interacting with other connected services or performing unintended operations. This represents an excessive permission grant, as the skill effectively inherits all capabilities of the `rube` MCP, not just those relevant to Polygon. To mitigate this, the `rube` MCP should be configured to only expose Polygon-specific tools to this skill, or the skill's interface should explicitly filter `tool_slugs` to only allow Polygon tools. Alternatively, the skill's description should explicitly state that it grants access to all tools available via `rube` MCP, making the broad scope transparent.	LLM	SKILL.md:64

Scan History

Embed Code

[![SkillShield](https://skillshield.io/api/v1/badge/b58af869353cf720.svg)](https://skillshield.io/report/b58af869353cf720)