Back to skill

Security audit

Polymarket Odds

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Polymarket public-data lookup tool with no credentials, persistence, or hidden local system changes.

Before installing, users should understand that the skill makes outbound requests to Polymarket's public API for market data. It does not require authentication or appear to read local private data, but tighter permission metadata and narrower trigger wording would improve transparency.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding

The skill performs network access to a public API but does not declare any tool scope such as permissions or allowed-tools. That creates an authorization and transparency gap: callers and the hosting agent may invoke a network-capable skill without explicit policy boundaries, making review, containment, and least-privilege enforcement harder.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The description includes broad invocation language such as use for questions about prediction markets, betting odds, market prices, event probabilities, or when the user asks about Polymarket data. Overly broad trigger text can cause the agent to select this skill in more situations than necessary, increasing unnecessary network calls and the chance of exposing user prompts or context to an external service.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.