AI agents call get_table_structure to retrieve information from MCP Vertica without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_table_structure' semantically aligns with querying table schema/metadata without modifying data. Given its position among other metadata-reading tools (list_indexes, list_views) on a database management server, it is most likely a non-destructive read operation. The empty description reduces confidence slightly, but the naming is sufficiently clear.
From the tool's definition Tool name 'get_table_structure' indicates retrieval of schema metadata. No description provided, but naming convention and context (alongside list_indexes, list_views) strongly suggests a read-only schema inspection operation.
Documented attack patterns abuse exactly the kind of access get_table_structure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Vertica, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table_structure:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_structure": {}
}
}get_table_structure 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.
get_table_structure. It is categorised as a Read tool in the MCP Vertica MCP Server, which means it retrieves data without modifying state.
Register the MCP Vertica MCP server in PolicyLayer and add a rule for get_table_structure: 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 Vertica. Nothing to install.
get_table_structure 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 get_table_structure 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 get_table_structure. 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.
get_table_structure is provided by the MCP Vertica MCP server (nolleh/mcp-vertica). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Vertica, 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.
6 MCP Vertica tools catalogued and risk-classified — across an index of 43,000+ MCP servers.