describe_table
AI agents call describe_table to retrieve information from Mcp Sqlite Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Describing a table retrieves its schema/metadata (columns, types, constraints) without modifying data or triggering external operations. This is a read operation with minimal blast radius. The tool appears part of a query-focused workflow alongside read_query and write_query siblings.
From the tool's definition Tool name 'describe_table' suggests retrieving table schema metadata; server description mentions 'querying' as a primary function, and sibling tools include 'read_query', indicating read-only operations.
Attacks that exploit this kind of access
describe_table. It is categorised as a Read tool in the Mcp Sqlite Manager MCP Server, which means it retrieves data without modifying state.
Register the Mcp Sqlite Manager 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 Mcp Sqlite Manager. 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 Mcp Sqlite Manager MCP server (jonnyhoff/mcp-sqlite-manager). 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 →