Published a month ago
Published a month ago
r_0xc137
Updated a month ago
0
Hi,
Today: reusable lists support IP/CIDR only. Everything else — User-Agent strings, URL paths, header values, Referer domains, JA4 fingerprints, account IDs — has to be enumerated inline in rule conditions.
Problem: the same values are duplicated across rules; adding one bad User-Agent means editing and republishing detection logic; rules grow into unreadable regex; and we can't populate values automatically from our threat intel or anti-fraud systems.
Request:
Benefit: separation of duties between on-call and rule author; automated list population from our own systems.
Windsley
Updated 25 days ago
0
Thank you for taking the time to write such a detailed request — it's clear you know the product well, and feedback like this is genuinely valuable to us 🙏 We fully agree with what you're describing and have discussed it internally at length. That said, we're sorry to say we don't currently have plans to bring this to the Community Edition.
Here's something we can share ahead of time: MCP support is on the way and will be released soon. Once it's available, you'll be able to use AI tools to add or remove entries like blocked IPs directly — no more configuring them one by one, which should make day-to-day management much easier.
Thanks again for the thoughtful feedback! If you'd like to share more about your setup and use case, we'd love to hear it — it really helps shape our future plans.
r_0xc137
Updated 24 days ago
0
Do you have plans to add this to Pro edition?
Windsley
Updated 24 days ago
Just to clarify, by “Community Edition,” I meant all current SafeLine editions—Personal, Lite, and Pro. So, for now, we don’t plan to add this feature to any of them, but we’ll continue to monitor user feedback and demand.