AI agents call is_table_exists to retrieve information from Duckdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple existence check on a table, which is a read-only operation that queries database metadata. It has no side effects, cannot modify data, and cannot execute arbitrary code. It falls squarely into the Read category with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'is_table_exists' and description 'Check if a table exists in the DuckDB database' indicate a query/inspection operation that retrieves metadata about database schema without modifying or executing arbitrary operations.
Attacks that exploit this kind of access
Check if a table exists in the DuckDB database. It is categorised as a Read tool in the Duckdb MCP Server, which means it retrieves data without modifying state.
Register the Duckdb MCP server in PolicyLayer and add a rule for is_table_exists: 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. Nothing to install.
is_table_exists 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 is_table_exists 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 is_table_exists. 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.
is_table_exists is provided by the Duckdb MCP server (synehq/mcp-server-duckdb). 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 →