List all views in the database
AI agents call list_views to retrieve information from Vertica 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 a read-only query of database metadata to enumerate views. It has no side effects, does not execute user-supplied code, does not modify data, and does not delete or move data. The blast radius of misuse is minimal—an agent listing views gains informational access but cannot interact with the views' underlying data or alter database state.
From the tool's definition Tool name 'list_views' and description 'List all views in the database' indicate a retrieval operation with no modification or execution of arbitrary logic. It retrieves metadata about database views, similar in nature to the sibling tool 'list_tables'.
Attacks that exploit this kind of access
List all views in the database. It is categorised as a Read tool in the Vertica MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vertica MCP Server MCP server in PolicyLayer and add a rule for list_views: 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 Vertica MCP Server. Nothing to install.
list_views 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 list_views 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 list_views. 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.
list_views is provided by the Vertica MCP Server MCP server (smith-nathanh/vertica-mcp-server). 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 →