describe_table
AI agents call describe_table to retrieve information from Trino MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
describe_table retrieves table structure information (columns, types, constraints, etc.) without modifying or executing against data. This is a standard read operation with no side effects. While the description is empty, the function name and context among other read-only metadata tools provide high confidence. Severity is low because misuse causes no data loss or execution of arbitrary logic.
From the tool's definition Tool name 'describe_table' indicates a descriptive/introspective operation. As a sibling to 'list_catalogs', 'list_schemas', 'list_tables', and 'get_table_stats', it is clearly part of the read-only metadata inspection family.
Attacks that exploit this kind of access
describe_table. It is categorised as a Read tool in the Trino MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trino 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 Trino 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 Trino MCP Server MCP server (weijie-tan3/trino-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 →