Get the schema (columns) and a few sample rows from the specified table.
AI agents call describe_table to retrieve information from SQLite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata (schema) and sample data from a table with no side effects. It is a query/inspection operation that neither modifies data, executes code, deletes records, nor commits financial transactions. The low severity reflects minimal risk even if misused — it exposes only schema structure and example rows, which may contain sensitive data but cannot be altered or cause operational damage.
From the tool's definition Tool description states 'Get the schema (columns) and a few sample rows from the specified table' — a read-only retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get the schema (columns) and a few sample rows from the specified table. It is categorised as a Read tool in the SQLite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SQLite MCP Server MCP server in PolicyLayer and add a rule for describe_table: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SQLite MCP Server. Nothing to install.
describe_table is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the describe_table rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for describe_table. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
describe_table is provided by the SQLite MCP Server MCP server (stevefordev/sqlite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →