Back to skill

Security audit

Book Tires

Security checks for vulnerabilities and agentic risk

Overview

This skill is for booking tire services, but it can contact an external booking service and create appointments with personal contact details without clear consent or confirmation instructions.

Before installing, confirm you are comfortable with the agent contacting Lokuli for tire searches and only allow it to create a booking after you have reviewed the provider, time, and contact details to be sent.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger language is overly broad because it activates on essentially any tires-related request, not just clear booking intent. That can cause the agent to invoke an external booking/search skill in contexts where the user only wants general information, increasing the chance of unnecessary data sharing or unintended third-party interaction.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill includes collection and transmission of personal data such as customer name, email, and phone number to a third-party MCP service, but it provides no warning, consent step, or disclosure to the user. In a booking context this creates privacy and compliance risk because the agent may solicit and forward sensitive contact details without making the external transfer explicit.

Static analysis

No suspicious patterns detected.