Compromised McpPublished Mar 27, 2026

MCP server offers a "safe-mode" flag that disables output sanitization

MediumAARM tierConfirmed
Seen14times across4customers
jiffy-ti-2026-000060

Summary

MCP server exposes a configuration flag named `safe_mode=false` that, when flipped, disables its own input/output sanitization. Attacker who can set the MCP server config (e.g., via a shared config file) flips it silently.

Severity & confidence

Severity
Medium

Medium

Notable weakness with plausible abuse chains or partial mitigations already in place. Track, and resolve as part of your normal hardening cadence.

Confidence
Confirmed

Confirmed

Observed directly by Jiffy scanners or validated by multiple independent sources. Indicators are reliable enough to drive automated action.

Indicators

Observed patterns and artifacts associated with this entry. Each indicator can be copied into your detection stack or SIEM.

  • (?i)safe_mode\s*[:=]\s*(?:false|no|0)

Detection rule

A YARA-style pseudo-rule auto-generated from the indicators above. Useful as a starting point — adapt the syntax for your target detection platform.

YARA-style pseudo-rule
rule jiffy_ti_2026_000060
{
    meta:
        source = "jiffy-intel"
        severity = "medium"
        description = "Auto-generated from Jiffy Intel indicators"
    strings:
    $content_pattern_0 = "(?i)safe_mode\\s*[:=]\\s*(?:false|no|0)"
    condition:
        $content_pattern_0
}

Auto-generated from the indicators above. Adapt syntax for your detection stack before deploying.

Affected tools

ToolVersionsStatus
Any MCP-capable agent*vulnerable

Example artifacts

Sanitized examples of artifacts Jiffy has observed exhibiting this pattern. Publisher handles are redacted; version ranges and status reflect the most recent scan.

  • content-filter-mcpMCP server
    Under review
    Source
    MCP Registry
    Versions
    1.0.0
    First observed
    Mar 19, 2026
  • safe-wrapper-mcpMCP server
    Quarantined
    Source
    Community registry
    First observed
    Mar 23, 2026

How to remediate

  1. 01Remove config toggles that disable safety logic.
  2. 02Safety must be unconditional.

Timeline & sources

Timeline

  1. First observedMar 19, 202629 days ago
  2. Last updatedApr 27, 2026today
  3. PublishedMar 27, 202621 days ago

Sources

scanner

References

Scan for patterns like this

Point Jiffy at your GitHub org, IDE config, or a single artifact. Get a scored report in under a minute.

Start a free scan