Is Byteask Embedded MCP server safe?
- Python shell/command execution
- MCP server launches a host command
- Python filesystem write/delete
What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.
Byteask Embedded MCP server is an MCP server analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: filesystem write, mcp tools detected and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
byteask-embedded-mcp 0.1.0
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of Byteask Embedded MCP server's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (4)
An MCP server entry launches a command on your host.
"command": "uv",
Why it matters: Trusting the manifest means running that binary — verify what it is and where it comes from.
Fix: Verify the launched command and its source before trusting this MCP server configuration.
The component can run operating-system commands or spawn processes.
subprocess.run(["ffmpeg", "-y", "-v", "error", "-i", os.path.join(tmp, "f%04d.png"),
"-vf", "palettegen=max_colors=128:stats_mode=diff", pal], check=True)subprocess.run(["ffmpeg", "-y", "-v", "error", "-framerate", str(FPS),
"-i", os.path.join(tmp, "f%04d.png"), "-i", pal,
"-lavfi", "paletteuse=dither=bayer:bayer_scale=3", "-loop", "0", OUT], c …Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.
Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; avoid shell=True.
The component writes or deletes files on disk.
shutil.rmtree(tmp, ignore_errors=True)
Why it matters: Usually legitimate, but worth confirming the paths can't be controlled by untrusted input.
Fix: Confirm which files are written/deleted and that paths cannot be influenced by untrusted input.
An MCP tool surface (manifest or tool definitions) was found.
"mcpServers": {mcp = FastMCP(
@mcp.tool(description=SEARCH_DOCS_DESCRIPTION)
@mcp.tool()
@mcp.tool(description=REQUEST_DOCUMENT_DESCRIPTION)
Why it matters: Just context — review which tools it offers and their permissions.
Fix: Review the declared MCP tools and their permissions.
How attackers abuse these capabilities
Interactive labs on the attack class behind the rules above. They show the technique, not anything found in Byteask Embedded MCP server.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →