Inspect the schema (column names and types) of a local file,
AI agents call analyze_schema to retrieve information from DuckDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs inspection/querying of schema metadata only. It does not create, modify, delete, or execute operations on data. The action is purely informational (Read category). Severity is low because schema inspection has minimal blast radius—the worst case exposes data structure information, not the data itself or system access.
From the tool's definition Tool name 'analyze_schema' and description 'Inspect the schema (column names and types)' indicate it retrieves metadata about data structure without modification.
Documented attack patterns abuse exactly the kind of access analyze_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DuckDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_schema:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_schema": {}
}
}analyze_schema 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.
Inspect the schema (column names and types) of a local file,. It is categorised as a Read tool in the DuckDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DuckDB MCP Server MCP server in PolicyLayer and add a rule for analyze_schema: 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 DuckDB MCP Server. Nothing to install.
analyze_schema 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 analyze_schema 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 analyze_schema. 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.
analyze_schema is provided by the DuckDB MCP Server MCP server (mustafahasankhan/duckdb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DuckDB MCP Server, 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.
5 DuckDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.