get_server_info

Get server configuration information including available database connections, default connection, and execution settings.

Server USQL MCP Server jvm/usql-mcp
Category Read
Risk class Low
Parameters 00 required

What get_server_info does on USQL MCP Server

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

Why get_server_info needs a policy

This tool retrieves and queries server configuration data without side effects. It does not execute code, modify data, delete resources, or move money. The blast radius of misuse is minimal—an attacker could learn about available databases and connections but cannot act upon them without using other tools like execute_query or execute_script.

From the tool's definition Tool name 'get_server_info' and description 'Get server configuration information including available database connections, default connection, and execution settings' indicate retrieval of configuration metadata with no modification or execution.

Questions about get_server_info

What does the get_server_info tool do? +

Get server configuration information including available database connections, default connection, and execution settings. It is categorised as a Read tool in the USQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_info? +

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

What risk level is get_server_info? +

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

Can I rate-limit get_server_info? +

Yes. Add a rate_limit block to the get_server_info 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 get_server_info completely? +

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

get_server_info is provided by the USQL MCP Server MCP server (jvm/usql-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.