AI agents call describe-table to retrieve information from Mcp Libsql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns schema information about database tables. Schema inspection is a non-destructive read operation with no side effects. It does not execute queries against data, modify tables, or perform any irreversible actions. Among sibling tools that include write-query and alter-table, this clearly sits in the Read category.
From the tool's definition Tool name is 'describe-table' and description states 'Table schema inspection with multiple output formats' — this retrieves and displays table metadata without modifying data.
Documented attack patterns abuse exactly the kind of access describe-table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Libsql, and nothing reaches the server without passing your rules. This is the rule we recommend for describe-table:
{
"version": "1",
"default": "deny",
"tools": {
"describe-table": {}
}
}describe-table is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Table schema inspection with multiple output formats. It is categorised as a Read tool in the Mcp Libsql MCP Server, which means it retrieves data without modifying state.
Register the Mcp Libsql 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 Libsql. 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 Libsql MCP server (xexr/mcp-libsql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Libsql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Mcp Libsql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.