PulseAugur
EN
LIVE 21:28:38

SchemaGate 1.1.0 adds column-level access control for LLMs

By PulseAugur Editorial · [1 sources] ·

SchemaGate 1.1.0 introduces column-level access control for LLMs, addressing a vulnerability where models could infer sensitive data from column names even if the table was restricted. The new feature allows users to define rules in a JSON file to hide specific columns from LLM prompts based on user roles. This prevents models from generating queries that access sensitive information like salaries or national IDs, improving data security for text-to-SQL applications. SchemaGate supports various databases and can be integrated as a Python library, CLI, or MCP server. AI

IMPACT Enhances data security for LLM-powered text-to-SQL applications by preventing sensitive column exposure.

RANK_REASON This is a product update for a data security tool that enhances LLM interactions with databases.

Read on dev.to — LLM tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

SchemaGate 1.1.0 adds column-level access control for LLMs

How we ranked this

Signal score
37 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
This is a product update for a data security tool that enhances LLM interactions with databases.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, infra
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — LLM tag TIER_1 English(EN) · Ashish sinha ·

    Hiding the table is not enough. Your LLM can still see the salary column.

    <p>Most text-to-SQL setups protect data at the table level. The analyst cannot read <code>hr_compensation</code>, so that table never goes into the prompt. Good.</p> <p>But a lot of sensitive data does not live in its own table. It lives in one column of a table everyone uses. <c…

RELATED ENTITIES

RELATED TOPICS