MCP server community
Risk level
high
75/100

neo4j-labs

neo4j-labs is a community-maintained MCP server from Neo4j Labs. Anomity scores its risk at 75 out of 100 (high). It matches 1 dangerous capability combination.

database:read database:write network:outbound credentials:access

Analysis summary

neo4j-labs is a community-maintained MCP server from Neo4j Labs. Anomity scores its risk at 75 out of 100 (high). It matches 1 dangerous capability combination.

Why this entry scored 75 out of 100

This profile starts at the catalog's neutral base of 50. Because the entry is community-maintained, trust adjusts the score by -10. Declared high-risk capabilities add +20 (capped at +30). It matches 1 dangerous capability combination, which contributes additional severity weight. The clamped result is 75, placing it in the high band.

See the full scoring formula →

Findings

  • Established community project Trust offset
    Contribution to score: -10
  • 2 high-risk capabilities: database:write, credentials:access Critical
    Contribution to score: +20
  • Database exfiltration risk (high) High
    Evidence
    Database read combined with outbound network can exfiltrate production data.
    Contribution to score: +15

Capabilities

Every capability the entry declares, with the security implication of each.

  • database:read Database read
    Reads from connected databases. Useful for query and analytics agents; risky when combined with outbound network.
  • database:write Database write
    Writes to connected databases. High-impact; combined with outbound network is treated as exfiltration-class.
  • network:outbound Outbound network
    Can make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access.
  • credentials:access Credentials access
    Reads provider API keys, OAuth tokens, or other secrets from the host keychain or environment.

Dangerous combinations matched

Capability pairings that compound into well-known attack patterns.

  • Database exfiltration risk high
    Database read combined with outbound network can exfiltrate production data.
    database:read network:outbound