KVKK/GDPR-compliant LLM-to-database gateway: PII masking, RBAC, rate limiting, audit log
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
query_tableQuery rows from a database table with optional filters. All results pass through the KVKK/GDPR gateway — sensitive fields are automatically masked.Query rows from a database table with optional filters. All results pass through the KVKK/GDPR gateway — sensitive fields are automatically masked.
No input schema was published for this tool.
list_tablesList all available database tables. Tables marked as 'deny' in gateway policy are omitted.List all available database tables. Tables marked as 'deny' in gateway policy are omitted.
No input schema was published for this tool.
describe_tableGet the column names and gateway masking policy for a table — helps the LLM understand what data it can access.Get the column names and gateway masking policy for a table — helps the LLM understand what data it can access.
No input schema was published for this tool.
query_audit_logQuery the gateway's own audit log — inspect which tools were called, on which tables, whether they were allowed or denied (and why), and which fields were redacted/written. Covers events since this server process started; count is capped by the gateway's audit.bufferSize (default 200).Query the gateway's own audit log — inspect which tools were called, on which tables, whether they were allowed or denied (and why), and which fields were redacted/written. Covers events since this server process started; count is capped by the gateway's audit.bufferSize (default 200).
No input schema was published for this tool.
gateway_statusShow the active gateway configuration: field masking rules, table policies, and audit settings.Show the active gateway configuration: field masking rules, table policies, and audit settings.
No input schema was published for this tool.
insert_rowInsert a new row into a database table. Only works for tables/roles explicitly granted insert access, and never for fields protected by a PII masking rule (e.g. tcKimlik, passwordHash).Insert a new row into a database table. Only works for tables/roles explicitly granted insert access, and never for fields protected by a PII masking rule (e.g. tcKimlik, passwordHash).
No input schema was published for this tool.
update_rowUpdate rows matching a filter in a database table. Requires a non-empty filter — cannot update an entire table. Refuses to touch more than the gateway's maxAffectedRowsPerWrite limit; narrow your filter if that happens.Update rows matching a filter in a database table. Requires a non-empty filter — cannot update an entire table. Refuses to touch more than the gateway's maxAffectedRowsPerWrite limit; narrow your filter if that happens.
No input schema was published for this tool.
delete_rowprivilegedDelete rows matching a filter from a database table. Requires a non-empty filter — cannot delete an entire table. Refuses to touch more than the gateway's maxAffectedRowsPerWrite limit; narrow your filter if that happens.Delete rows matching a filter from a database table. Requires a non-empty filter — cannot delete an entire table. Refuses to touch more than the gateway's maxAffectedRowsPerWrite limit; narrow your filter if that happens.
No input schema was published for this tool.
8 of 8 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
KVKK/GDPR-compliant LLM-to-database gateway: PII masking, RBAC, rate limiting, audit log
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+43 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.