search_columns

Search for column names containing the given text across tables/views. Useful before writing SQL joins or filters.

Server OpenLink MCP Server for ODBC pvsmark/pvs-odbc-mcp
Category Read
Risk class Low
Parameters 00 required

What search_columns does on OpenLink MCP Server for ODBC

AI agents call search_columns to retrieve information from OpenLink MCP Server for ODBC without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_columns needs a policy

This tool performs metadata discovery by searching column definitions. It retrieves information only and cannot create, modify, delete, or execute operations. Confidence is high because the purpose is clearly informational. Severity is low because column name metadata is typically non-sensitive and exposure is limited to schema information that doesn't directly affect data integrity or business operations.

From the tool's definition Tool searches and retrieves column names across tables/views without modifying data. The description explicitly states it is 'useful before writing SQL joins or filters'—a query/discovery operation with no side effects.

Questions about search_columns

What does the search_columns tool do? +

Search for column names containing the given text across tables/views. Useful before writing SQL joins or filters. It is categorised as a Read tool in the OpenLink MCP Server for ODBC MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_columns? +

Register the OpenLink MCP Server for ODBC MCP server in PolicyLayer and add a rule for search_columns: 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 OpenLink MCP Server for ODBC. Nothing to install.

What risk level is search_columns? +

search_columns is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_columns? +

Yes. Add a rate_limit block to the search_columns 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.

How do I block search_columns completely? +

Set action: deny in the PolicyLayer policy for search_columns. 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.

What MCP server provides search_columns? +

search_columns is provided by the OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.