Get the schema information for a specific table
AI agents call describe_table to retrieve information from Server Puppeteer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database schema information (table structure, columns, data types, constraints, etc.) without side effects. It is a passive query operation typical of schema inspection utilities. No data is modified, no code is executed, and no deletions occur. The low severity reflects minimal blast radius—an AI agent misusing this would at most access unintended schema metadata, which is informational only.
From the tool's definition Tool name 'describe_table' and description 'Get the schema information for a specific table' indicate a read-only query operation that retrieves metadata without modifying or executing code.
Attacks that exploit this kind of access
Get the schema information for a specific table. It is categorised as a Read tool in the Server Puppeteer MCP Server, which means it retrieves data without modifying state.
Register the Server Puppeteer 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 Server Puppeteer. 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 Server Puppeteer MCP server (@hisma/server-puppeteer). 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 →