Security audit

Datetime Tool

Security checks for vulnerabilities and agentic risk

Overview

This is a low-impact date/time utility whose documentation overstates its actual features, but the inspected artifacts do not show hidden access, persistence, network use, or destructive behavior.

Install only if you need a simple local date/time helper, and do not rely on the advertised advanced timezone conversion, precise month/year arithmetic, JSON output, or natural-language parsing until the publisher fixes the documentation or implementation.

A.I.G

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

SkillSpector

Vulnerability Patterns

MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
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 (5)

Tp4

High

Category: MCP Tool Poisoning
Confidence: 98% confidence
Finding: The code is clearly a date/time utility, so the high-level domain matches the description. However, the declared description materially overstates capability. There is no timezone handling or conversion at all. Natural language parsing is only a minimal 'relative' command for a few phrases, and that function appears buggy because it expects two tokens while examples like 'tomorrow' and 'yesterday' are single-token inputs. The tool supports only a small fixed set of input formats and simple arithmetic, with months/years approximated in some cases. Therefore the description does not accurately represent the implemented behavior.
Content: No source excerpt is available for this finding.

Tp4

High

Category: MCP Tool Poisoning
Confidence: 95% confidence
Finding: The code broadly matches a date/time utility and does include formatting, basic timezone handling, calendar display, relative time, and date arithmetic. However, the declared description overstates the implementation in several material ways. There is no natural language parsing (e.g. inputs like 'next Friday' or 'tomorrow at noon' are unsupported). Format support is limited to a handful of hardcoded patterns rather than a comprehensive toolkit. Additionally, month/year arithmetic is implemented as rough day-count approximations rather than true calendar-aware arithmetic. There are no suspicious undeclared capabilities or resource accesses; the mismatch is primarily that the description promises broader functionality than the code actually provides.
Content: No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The manifest describes a comprehensive toolkit with timezone conversions and natural language parsing, but the implementation never uses timezone-aware datetime handling and has no conversion between timezones. Its 'natural language parsing' is limited to a rigid two-token parser for cases like 'next week', and even rejects single-word examples such as 'tomorrow' and 'yesterday'.
Content: No source excerpt is available for this finding.

Intent-Code Divergence

Medium

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The docstring says the function parses relative time like 'tomorrow' and 'yesterday', and the CLI help repeats that claim. However, the code immediately requires exactly two whitespace-separated tokens, so single-word inputs like 'tomorrow' and 'yesterday' trigger an error path instead of being parsed.
Content: No source excerpt is available for this finding.

Description-Behavior Mismatch

Low

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The manifest describes a comprehensive toolkit with natural language parsing and timezone conversions, but the implementation only parses a small hardcoded set of timestamp/date formats and a single HH:MM format for timezone handling. There is no natural-language parsing such as 'tomorrow' or 'next Friday', and timezone support is limited to showing/localizing a time in one specified timezone rather than converting between timezones.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.