Back to skill

Security audit

regmapper

Security checks for vulnerabilities and agentic risk

Overview

This skill coherently connects an agent to the RegMapper API for regulatory research and project annotations, with its read and write capabilities disclosed and scoped by the user's RegMapper token permissions.

Install this only if you trust RegMapper with the projects your API token can access. Use a least-privilege token where possible, keep REGMAPPER_API_TOKEN out of source control, and review agent actions before creating or updating shared project comments because those changes persist in RegMapper.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The comment endpoints can return full note content, including project annotations that may contain sensitive internal compliance discussions or personal data. In an agent setting, insufficiently explicit privacy signaling increases the chance the model retrieves and surfaces confidential note text to the user when only summaries or metadata were needed.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
76% confidence
Finding

The manifest says the skill is for browsing, searching, and annotating regulations, which strongly implies read-oriented access plus annotation creation. However, the OpenAPI spec also exposes PATCH-based comment updates in addition to creation, meaning the skill can modify existing remote project records, not just add annotations. That is a meaningful behavior expansion beyond the simpler description.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
80% confidence
Finding

The POST and PATCH comment endpoints perform data-changing operations by creating or altering stored comments, notes, statuses, or categories. Although permissions are noted, the documentation does not explicitly warn that these actions change persisted project data and may affect collaboration records or audit-sensitive content.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Low
Category
Not specified by scanner
Confidence
71% confidence
Finding

The manifest focuses on regulations, compliance requirements, annotations, and comparing regulation versions. The schemas for comparison responses additionally provide orig_url and copyright_url fields, which surface external document and copyright links unrelated to the core annotation/search workflow. This is a supplementary capability not reflected in the stated purpose.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.