|
|
|
|
|
|
by munio
90 days ago
|
|
|
Cool use case. One thing worth thinking about with any MCP server that does file parsing — the tool definitions themselves can be a security surface. Things like path parameters without validation, or deserialization from untrusted save files. Even "read-only" MCP servers can be vectors if an attacker controls the input file. Not specific to your project, just something I've been seeing across a lot of MCP implementations. |
|
|