More screenshots
Works with the AI Agents you already use
PII in Logs Check
Logs are copied to more places, and read by more people, than the database the data came from.
$5
PII in Logs Check
Example session with this skill installed
Check this project with pii-in-logs-check.
- Read your context and instructions
- Compiled the pii in logs
$ python3 scripts/check_pii_logs.py examples/risky
BLOCK app/auth.py:13 P04 LOGIN_BODY_LOGGED
logger.info("login attempt %s", request.form)
Why: A login, sign-up or password handler logs the whole request body or form. That body holds the user's password in clear text, so every login writes a password to the log.
Safer: Log the user id or username and the outcome only. If you need the body, remove the password fields first (an allow-list of fields is safer than a block-list).
BLOCK app/auth.py:15 P01 SECRET_LOGGED
BLOCK app/auth.py:27 P03 CARD_DATA_LOGGED
BLOCK billing/Program.cs:21 P01 SECRET_LOGGED
BLOCK gateway/middleware.go:11 P02 AUTH_HEADER_OR_SESSION_LOGGED
BLOCK src/server.js:6 P02 AUTH_HEADER_OR_SESSION_LOGGED
REVIEW app/auth.py:19 P11 PERSONAL_DATA_LOGGED
REVIEW app/auth.py:26 P14 REQUEST_BODY_LOGGED
REVIEW app/monitoring.py:7 P18 ERROR_TRACKER_SENDS_PII
REVIEW billing/Program.cs:8 P17 SQL_VALUES_LOGGING_ON
REVIEW billing/Program.cs:12 P16 HTTP_DETAILS_LOGGING_ON
REVIEW billing/Program.cs:20 P11 PERSONAL_DATA_LOGGED
REVIEW gateway/middleware.go:13 P19 LABELLED_SECRET_LOGGED
REVIEW src/main/java/com/example/shop/CustomerService.java:18 P12 ID_OR_BANK_NUMBER_LOGGED
REVIEW src/main/resources/application.properties:2 P15 DEBUG_LEVEL_IN_PRODUCTION
REVIEW src/main/resources/application.properties:3 P16 HTTP_DETAILS_LOGGING_ON
REVIEW src/main/resources/application.properties:5 P17 SQL_VALUES_LOGGING_ON
REVIEW src/server.js:9 P13 WHOLE_OBJECT_LOGGED
REVIEW src/server.js:14 P13 WHOLE_OBJECT_LOGGED
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 7 files, 7 with logging 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
console.log("login", req.body) in a login route writes every user's password to your log service, and log.info("user={}", user) prints every field of the user object, password hash included. Logs are copied to more places, and read by more people, than the database the data came from. This skill finds those and eleven other logging mistakes before they ship, and tells you how to fix each one.
Your agent runs a scanner on Python, JavaScript and TypeScript, Java, Kotlin, Go, Ruby, PHP and C# code, and on Spring Boot application.properties and application.yml, ASP.NET Core appsettings.json, logback and log4j files, sentry.properties and .env.production. It finds each logging or print call (Python logging, structlog, print; console, pino, winston, NestJS; SLF4J, Log4j, Android Log, kotlin-logging; Go log, slog, zap, logrus; Rails logger; Laravel Log, error_log; ILogger, Serilog) and reads what it writes: arguments, object keys, f-strings and template strings, and the value after a label such as "password=%s" or a {Password} template hole. It knows when a value is only tested, measured, cut or masked (token is None, len(token), token[:6], mask(card)) and that an exception is not a secret (logger.error("Failed to refresh token: %s", e)). It honours pino redact paths for object keys in pino calls, Go LogValuer types, and types declared in the same file with their secret fields kept out of logs (SecretStr, field(repr=False), @ToString.Exclude, [NotLogged]). It skips only dev, development, local, test, ci and staging profiles, and treats print output of command-line tools as output, not logs, while Lambda handlers, Celery tasks and web apps still count as logs. It never runs your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- P01: passwords, tokens, API keys, client and AWS secret access keys, private keys, one-time codes, database connection strings and URLs, or the whole environment written to a log or printed
- P02: Authorization, Cookie or API-key header values (also through HttpHeaders.AUTHORIZATION and HeaderNames.Authorization), a request's session id or cookies, morgan :req[authorization], or Authorization added to ASP.NET Core HTTP logging
- P03: card numbers and CVV/CVC security codes
- P04: the whole body or form of a login, sign-up or password request
REVIEW
- P11: email addresses, phone numbers, postal addresses and dates of birth
- P12: social security, national id, passport, tax and driver's license numbers, IBANs, bank account, routing and medical record numbers
- P13: whole user, customer, account or request objects, login or sign-up request objects, header sets and request sessions
- P14: whole request bodies, forms, query strings and parameter collections
- P15: DEBUG or TRACE as the root or default level in production configuration (Spring Boot, appsettings.json, logback, log4j, Rails production.rb, .env.production, a Django production root logger)
- P16: HTTP body or header logging switched on outside a development check (ASP.NET Core HttpLoggingFields, Spring log-request-details and request logging filters, OkHttp HttpLoggingInterceptor without redactHeader, Python http.client debuglevel, Go httputil.DumpRequest)
- P17: SQL parameter values in logs (EF Core EnableSensitiveDataLogging outside a development check, Hibernate bind logger at TRACE)
- P18: Sentry send-default-PII switched on, or a dataCollection / data_collection setting that leaves user info, cookies, headers or bodies on
- P19: a neutrally named value logged right after a message label that names a secret ("password: %s", value)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and source (OWASP, CWE, PCI SSC, Microsoft, Sentry) for each rule
- A risky and a safe example project in five languages, and the real report the scanner produces on the risky one
Limits It decides by names: a value in a variable called x or result is reported only when a label, a key or an assignment in the same file says what it holds, and values passed through other files are not followed. Redaction done in custom log filters or masking patterns is not seen. IP addresses and user names are not reported, because the OWASP Logging Cheat Sheet recommends recording them for security events. A JavaScript SDK 11 Sentry.init without dataCollection is not reported, because the SDK version is not read. NOT FLAGGED is not a guarantee.
Static check of source and configuration text. Values built in other files, custom redaction filters and logging settings in deployment files are not followed. 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 4 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project holds no real secrets or personal data. Its files are inert samples for the scanner to read; they are never run.