Back to skill

Security audit

Polymarket Odds

Security checks for vulnerabilities and agentic risk

Overview

This skill is a read-only Polymarket lookup tool that makes disclosed public API requests and does not show hidden, destructive, persistent, or credential-seeking behavior.

Install this only if you are comfortable with market search terms and token IDs being sent to Polymarket public APIs. Treat returned odds as market data, not financial advice; the skill does not place trades or use an account.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 28)May include surrounding context.

md
The CLI is at `polymarket.mjs` in this skill folder. Run with:

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
94% confidence
Finding

The skill documentation advertises and directs use of a CLI that makes outbound network requests to public Polymarket APIs, but the skill manifest does not declare any explicit tool scope such as permissions or allowed-tools. This creates a policy and review gap: an agent may invoke network-capable code without transparent authorization boundaries, making the skill harder to audit and increasing the risk of unintended data egress or unapproved external access.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.