More screenshots
Works with the AI Agents you already use
Message Broker Config Check
This skill finds those and six other kinds of message broker mistakes before the broker goes live, and tells you how to fix each one.
$5
Message Broker Config Check
Example session with this skill installed
Check this project with message-broker-config-check.
- Read your context and instructions
- Compiled the message broker config
$ python3 scripts/check_broker.py examples/risky
BLOCK kafka/config/server.properties:6 B01 ANONYMOUS_ACCESS_ON_NETWORK
listeners=PLAINTEXT://:9092,CONTROLLER://:9093,SASL_PLAINTEXT://0.0.0.0:9094
Why: Clients can connect without a username or password on a listener that is not bound to localhost: Mosquitto allow_anonymous true, a Kafka PLAINTEXT listener (or SSL without client certificates) with no authorizer, NATS with no authorization or with no_auth_user, or a RabbitMQ anonymous_login_user. Anyone who can reach the port can read, publish and (on Kafka) delete data.
Safer: Require credentials on every listener that is reachable from other hosts (password_file, SASL, NATS users or accounts, client certificates) and bind test-only anonymous listeners to 127.0.0.1.
BLOCK kafka/config/server.properties:14 B04 SECRET_IN_CONFIG
BLOCK kafka/config/server.properties:15 B04 SECRET_IN_CONFIG
BLOCK kafka/config/server.properties:18 B03 KAFKA_ALLOW_EVERYONE_IF_NO_ACL
BLOCK mosquitto/config/mosquitto.conf:7 B01 ANONYMOUS_ACCESS_ON_NETWORK
BLOCK mosquitto/config/mosquitto.conf:17 B04 SECRET_IN_CONFIG
BLOCK nats/nats-server.conf:3 B01 ANONYMOUS_ACCESS_ON_NETWORK
BLOCK nats/nats-server.conf:14 B04 SECRET_IN_CONFIG
BLOCK rabbitmq/rabbitmq.conf:7 B04 SECRET_IN_CONFIG
BLOCK rabbitmq/rabbitmq.conf:10 B02 RABBITMQ_GUEST_REMOTE_OR_DEFAULT_PASSWORD
BLOCK rabbitmq/rabbitmq.conf:12 B02 RABBITMQ_GUEST_REMOTE_OR_DEFAULT_PASSWORD
BLOCK rabbitmq/rabbitmq.conf:18 B01 ANONYMOUS_ACCESS_ON_NETWORK
BLOCK rabbitmq/rabbitmq.conf:19 B04 SECRET_IN_CONFIG
REVIEW kafka/config/server.properties:6 B11 PLAIN_TEXT_LISTENER_ON_NETWORK
REVIEW kafka/config/server.properties:19 B13 KAFKA_TOPIC_AUTO_CREATE
REVIEW mosquitto/config/mosquitto.conf:6 B11 PLAIN_TEXT_LISTENER_ON_NETWORK
REVIEW mosquitto/config/mosquitto.conf:9 B11 PLAIN_TEXT_LISTENER_ON_NETWORK
REVIEW nats/nats-server.conf:3 B11 PLAIN_TEXT_LISTENER_ON_NETWORK
REVIEW nats/nats-server.conf:4 B12 MANAGEMENT_UI_ON_NETWORK
REVIEW nats/nats-server.conf:12 B14 CLUSTER_PORT_WITHOUT_AUTH
REVIEW rabbitmq/rabbitmq.conf:2 B11 PLAIN_TEXT_LISTENER_ON_NETWORK
REVIEW rabbitmq/rabbitmq.conf:15 B12 MANAGEMENT_UI_ON_NETWORK
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 4 files, 4 with message broker config content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
loopback_users = none in rabbitmq.conf lets guest/guest log in from any host, and listeners=PLAINTEXT://:9092 in a Kafka server.properties with no authorizer lets anyone who can reach the port read, write and delete topics. This skill finds those and six other kinds of message broker mistakes before the broker goes live, and tells you how to fix each one.
Your agent runs a scanner on your broker configs: RabbitMQ (rabbitmq.conf, conf.d files, advanced.config), Mosquitto (mosquitto.conf), Kafka (server.properties, broker.properties, controller.properties) and NATS (nats.conf, nats-server.conf), plus .conf files in a conf.d folder or next to those files (such as /etc/mosquitto/conf.d/default.conf), whose format it works out from the content. It reads each format the way the broker does (Erlang terms, per-listener Mosquitto settings, Java properties with line continuation, NATS blocks and arrays) and knows each broker's defaults: RabbitMQ listens on every interface and keeps guest on localhost, Mosquitto 2.x refuses anonymous clients once a listener is defined, an empty Kafka listener host binds every interface and KRaft controller listeners default to PLAINTEXT, and NATS listens on 0.0.0.0. It never connects to a broker. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- B01: clients let in without credentials on a network listener (Mosquitto allow_anonymous true, Kafka PLAINTEXT or SSL without client certificates and no authorizer, NATS with no authorization or with no_auth_user, RabbitMQ anonymous_login_user)
- B02: the RabbitMQ guest user allowed from remote hosts, or default_pass set to guest, the user name or a common word
- B03: Kafka allow.everyone.if.no.acl.found=true
- B04: passwords, tokens and keys written in the config (RabbitMQ default_pass and ssl_options.password, Mosquitto bridge remote_password, Kafka keystore passwords, inline private keys and sasl.jaas.config, NATS passwords, tokens and route URLs)
REVIEW
- B11: listeners reachable from the network without TLS, including plain RabbitMQ 5672 left open next to a TLS listener
- B12: the RabbitMQ management UI (HTTP or HTTPS) or the NATS monitoring port on every interface
- B13: Kafka topic auto-creation on (auto.create.topics.enable=true, or not set)
- B14: NATS cluster or gateway ports without authorization
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example project (RabbitMQ, Mosquitto, Kafka and NATS configs), and the real report the scanner produces on the risky one
Limits It reads each file on its own: settings in one conf.d or include file are not combined with another, and environment variables and command-line flags (Docker RABBITMQ_* and KAFKA_* variables), password and ACL files, Kafka ACLs stored in the cluster, enabled plugins and firewalls are not checked. Mosquitto rules assume version 2.x. NOT FLAGGED is not a guarantee.
Static check of broker config text. Values set through environment variables, included files or the broker's own database are not seen, and a listener on a private address counts as reachable from the network. Stock quick-start configs (the Kafka quick-start, the NATS Docker image config) are reported because they are open by design for local development. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example configs include clearly fake, inert passwords (NOTREAL, not-a-real-...) and made-up host names for the scanner to find. Nothing in them is started or contacted.