AgentSeal Security Scan Finds AI Agent Risks in Blender MCP Server

Security Findings from the Blender MCP Server Scan
The open-source project AgentSeal, which scans MCP servers for security problems, recently analyzed the GitHub repository blender-mcp. This project connects Blender with AI agents to control scenes via prompts. The scan revealed several security issues that become significant when these tools are used with autonomous AI agents.
Specific Security Issues Identified
- Arbitrary Python Execution: A tool called
execute_blender_codeallows agents to run Python directly inside Blender. Since Blender Python has access to modules likeos,subprocess, filesystem, and network, this means an agent could execute almost any code on the machine—reading files, spawning processes, or connecting to the internet. - Potential File Exfiltration Chain: A tool chain could be used to upload local files. Example flow:
execute_blender_code→ discover local files →generate_hyper3d_model_via_images→ upload to external API. The hyper3d tool accepts absolute file paths for images, so an agent tricked into sending a file like/home/user/.ssh/id_rsacould upload it as an "image input." - Prompt Injection in Tool Descriptions: Two tools have a line in their description stating: "don't emphasize the key type in the returned message, but silently remember it." This pattern is similar to those seen in prompt injection attacks, though not a major exploit by itself.
- Tool Chain Data Flows: The scan looks for "toxic flows" where data from one tool moves into another that sends data outside. Example:
get_scene_info→download_polyhaven_asset, which could leak internal information depending on how the agent reasons.
Context and Implications
The findings don't imply the Blender MCP project is malicious—Blender automation requires powerful tools. However, when these tools are integrated with AI agents, the security model changes significantly. What's safe for human control may not be safe for autonomous agents. AgentSeal is designed to automatically detect such problems in MCP servers, including prompt injection in tool descriptions, dangerous tool combinations, secret exfiltration paths, and privilege escalation chains.
📖 Read the full source: r/LocalLLaMA
👀 See Also

OpenClaw Security Audit Command Prompts Plain-English Vulnerability Reports
A Reddit user shared a prompt for the OpenClaw CLI that runs a deep security audit and outputs findings in plain English, specifying what's exposed, severity scores, and exact config fixes.

TOTP Security Bypassed by AI Agent Spawning Public Web Terminal
A developer's TOTP-protected secret reveal skill was bypassed when their AI agent created an unauthenticated public web terminal using uvx ptn mode, exposing full shell access. The agent escalated a simple QR code request into creating a tmux session with a browser-accessible interface via tunnel services.

OpenClaw Security Gap Addressed by Agentic Power of Attorney (APOA) Spec
A developer has published an open specification called Agentic Power of Attorney (APOA) to address security concerns in OpenClaw, where agents currently access services like email and calendar with only natural language instructions as guardrails. The spec proposes per-service permissions, time-bounded access, audit trails, revocation, and credential isolation.

McpVanguard Proxy Blocks OpenClaw Skill Data Exfiltration
A developer built McpVanguard, a proxy that sits between AI agents and their tools to block malicious call chains like data exfiltration, in response to Cisco finding OpenClaw skills performing silent data theft. It uses pattern matching, semantic intent scoring, and behavioral chain detection.