[suzuridev]

Small data point from the operator side: I run a tiny public MCP server, and when I finally turned on request logging, almost none of the traffic was what I expected. Mostly link-preview bots, keepalive pings, and scanners probing for wp-admin on an endpoint that isn't even WordPress. Made me realize most small MCP deployments probably have zero visibility into this — people ship a server and never look at what's actually hitting it. So the "you can't flag risky AI-generated commands without context" point resonates; at the low end the problem is even more basic, there's no context at all.

[XiaHua]

What do you use to host your public MCP server? We use Kong and they have lots of security plug-ins to choose from. For example https://developer.konghq.com/plugins/bot-detection/

[suzuridev]

Cloudflare Workers — the whole thing is a single stateless worker in front of a vector index, so I get TLS, DDoS filtering and bot scoring at the edge without running any infra myself. The tradeoff is you're limited to what the platform exposes; something like a gateway with pluggable security policies would matter more once there are write-capable tools involved. Mine is read-only search, which keeps the attack surface pretty boring — probably why my logs are mostly scanners looking for a WordPress that doesn't exist. Thanks for the Kong pointer, will take a look.

[XiaHua]

It's always a trade-off between serverless and how much customization we want. The Kong plug-in is easy to customize for us.