MCP server community
Risk level
critical
100/100

Blender MCP ↗

Blender MCP is a community-maintained MCP server from Blender community. Anomity scores its risk at 100 out of 100 (critical). It matches 3 dangerous capability combinations.

shell:execute filesystem:read filesystem:write network:outbound

Analysis summary

Blender MCP is a community-maintained MCP server from Blender community. Anomity scores its risk at 100 out of 100 (critical). It matches 3 dangerous capability combinations.

An MCP server that connects an agent to Blender's Python API, letting a model create and modify 3D scenes, run geometry operations, and render — driving a desktop application through scripted commands.

The capability that matters is that Blender's Python API is general-purpose Python. A server exposing it is effectively exposing code execution on the host, which is why this entry declares shell execution alongside filesystem access and outbound network — a combination Anomity flags as full control. That is not a criticism of the project, it is the honest shape of scripting-API bridges generally. Run it in a sandbox or a container, not on the workstation holding your signing keys.

Why this entry scored 100 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 3 dangerous capability combinations, which contribute additional severity weight. The clamped result is 100, placing it in the critical band.

See the full scoring formula →

Findings

  • Established community project Trust offset
    Contribution to score: -10
  • 2 high-risk capabilities: shell:execute, filesystem:write Critical
    Contribution to score: +20
  • Data exfiltration risk (high) High
    Evidence
    Shell execution combined with outbound network access can exfiltrate arbitrary data from the machine.
    Contribution to score: +15
  • Persistence + execution risk (medium) Medium
    Evidence
    Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts).
    Contribution to score: +5
  • Full-control risk (critical) Critical
    Evidence
    Shell + filesystem write + network is effectively a remote shell on the employee machine.
    Contribution to score: +25

Capabilities

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

  • shell:execute Shell execution
    Can run arbitrary shell commands. Combined with network access this becomes effectively a remote shell.
  • filesystem:read Filesystem read
    Can read files on the host system. Used for context, indexing, or analysis.
  • filesystem:write Filesystem write
    Can create, edit, or delete files on the host system. High-impact capability — anything from helpful edits to planting persistence.
  • 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.

Dangerous combinations matched

Capability pairings that compound into well-known attack patterns.

  • Data exfiltration risk high
    Shell execution combined with outbound network access can exfiltrate arbitrary data from the machine.
    shell:execute network:outbound
  • Persistence + execution risk medium
    Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts).
    shell:execute filesystem:write
  • Full-control risk critical
    Shell + filesystem write + network is effectively a remote shell on the employee machine.
    shell:execute filesystem:write network:outbound