Viewing profile — kerlenton

[dead]

Ha, fair. tshark in a shell works fine, the only reason to wrap it is typed output and not handing the agent a raw shell.

[dead]

Thanks, that means a lot. Would love to hear how it goes once you try it

There's nothing redacted because the header isn't collected in the first place. Under http mode, the proxy intercepts the JSON-RPC messages, but not their headers, so there's no wa…

[dead]

Maybe, but I didn't do it. Perhaps people are boosting their karma?

[dead]

Thanks a lot!

Thank you! Showing the data in a web page should definitely be possible. But I’m not sure if this matches the original idea I had, where the tool would run in the terminal only. Wh…

Thanks! Actually, there is already an MCP for Wireshark, for example https://github.com/0xKoda/WireMCP

[flagged]

[flagged]

[flagged]

[flagged]

Makes sense. 3 generic tools + summarize first is a nice approach to sidestepping the problem of too many tools. But it looks like it shifts the chokepoint around rather than elimi…

Multiplexing the agents is clearly the first obvious pain point, but the other one I keep encountering after this is visibility: with multiple agents running, it becomes difficult …

The catalog approach is appropriate for MCP as well. Something I would be interested in: once you have all of your services/APIs/DBs exposed via one MCP server, the next choke poin…

The deterministic MCP server testing without any LLM in the loop is actually pretty useful for CI. However, the issue that I run into consistently is a level above: the server can …

A helpful place to start. One item that I would point out is that many authorities exist at the time of running the program rather than in the configuration or tool definition. So …

The approach you described to recording and replaying actions seems interesting. I went at this problem from a different perspective, though. I developed a wiretap transparent prox…