List all projections in the database (Vertica-specific)
AI agents call list_projections 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 queries database metadata to enumerate projections. It retrieves schema information (similar to the sibling 'list_tables' and 'list_views' tools) with no side effects, no code execution, and no data deletion or creation. The blast radius of misuse is minimal—an AI agent could only read database structure metadata.
From the tool's definition Tool name 'list_projections' and description 'List all projections in the database' indicate a retrieval operation. Vertica projections are pre-computed views/materialized structures.
Attacks that exploit this kind of access
List all projections in the database (Vertica-specific). 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_projections: 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_projections 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_projections 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_projections. 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_projections 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 →