List available SQL dialects and their capabilities.
AI agents call list_dialects to retrieve information from Orionbelt Semantic Layer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple informational lookup that queries metadata about available SQL dialects and their supported features. It has no side effects, does not execute code, and does not modify or delete data. It is purely a retrieval operation, falling clearly into the Read category with low severity since misuse poses minimal risk—an agent could at most retrieve dialect information that is already public metadata.
From the tool's definition Tool name 'list_dialects' and description 'List available SQL dialects and their capabilities' indicate a read-only operation that retrieves information about supported SQL dialects without modifying any data or executing queries.
Attacks that exploit this kind of access
List available SQL dialects and their capabilities. It is categorised as a Read tool in the Orionbelt Semantic Layer MCP Server, which means it retrieves data without modifying state.
Register the Orionbelt Semantic Layer MCP server in PolicyLayer and add a rule for list_dialects: 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 Orionbelt Semantic Layer. Nothing to install.
list_dialects 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_dialects 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_dialects. 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_dialects is provided by the Orionbelt Semantic Layer MCP server (ralfbecher/orionbelt-semantic-layer-mcp). 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 →