Back to skill

Security audit

Polymarket API

Security checks for vulnerabilities and agentic risk

Overview

This skill coherently provides read-only Polymarket market lookups using a disclosed public API.

Install only if you are comfortable with the agent making read-only calls to Polymarket's public API for market data. For tighter control, invoke it only for Polymarket-specific questions or market slugs.

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
90% confidence
Finding

The skill invokes a Python script that makes outbound network requests to Polymarket's public API, but the manifest does not declare any explicit tool scope such as permissions or allowed-tools. This creates a governance gap: the skill can access the network without a clearly documented or constrained authorization boundary, making review and policy enforcement harder.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger description is broad enough to match general questions about betting odds, market prices, event probabilities, or Polymarket data, which may cause the skill to be invoked in contexts where it is not strictly necessary. Overbroad invocation increases the chance of unnecessary external calls and data handling, and can route user queries to this skill when a narrower tool would be safer or more appropriate.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.