you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 3 months ago (2 children)

This is pretty much entirely why I built https://github.com/SteffenBlake/cli-mcp-mapper

I map bespoke CLI commands, with parameters, to MCP tools, and then 100% just turn off the ability to invoke the CLI itself entirely.

That way it can only explicitly invoke the whitelisted commands I have granted it access to run, with only the parameters I have allowed it to.

So for example I can explicitly expose git commit, status, stage, unstage, but everything else git related is not available, not even git push or pull.

This substantially seems to help prevent the LLM from going off the rails on stupid CLI nonsense, like when it starts cating files instead of just fucking reading them.

  • source
  • hideshow 2 child comments
  • [–] 3 points 3 months ago (1 child)

    That's a good idea. Be careful of the more advanced models finding ways to abuse/circumvent it though, even with only a limited set of parameters. Eg. A lot of git commands can be tricked into dropping into less which can drop into a full shell.

    They know all the gtfobins.org tricks.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 3 months ago

    It should theoretically be impossible with the way you set it up.

    You explicitly, opt in, expose which parameters are available to the LLM, it cant invoke any params beyond that.

    And you can set params to hard values that arent exposed.

    Finally, you can use the enum config to further specify a whitelist of valid values for a param, anything else gets rejected.

    This pretty much locks most tools down tight.

    Though, wouldn't hurt to add integration tests covering scenarios like this explicitly.

  • source
  • parent