Check if a table exists in the database
AI agents call table_exists to retrieve information from MCP PostgreSQL Server 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 metadata check (existence verification) on a database table. It is a read-only operation that queries the database schema but produces no side effects, no data modifications, and no irreversible actions. The server description emphasizes 'secure read-only access' and the tool's function aligns with inspecting table structures.
From the tool's definition Tool name 'table_exists' and description 'Check if a table exists in the database' indicate a query operation that retrieves metadata without modifying data.
Attacks that exploit this kind of access
Check if a table exists in the database. It is categorised as a Read tool in the MCP PostgreSQL Server MCP Server, which means it retrieves data without modifying state.
Register the MCP PostgreSQL Server MCP server in PolicyLayer and add a rule for 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 MCP PostgreSQL Server. Nothing to install.
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 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 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.
table_exists is provided by the MCP PostgreSQL Server MCP server (kristofer84/mcp-postgres). 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 →