Get a single example by name with its query and compiled SQL preview.
AI agents call get_example 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.
The tool retrieves and displays metadata about an example (its query definition and a SQL preview). It does not execute queries against a database, modify data, or trigger external operations. This is a straightforward data retrieval function analogous to 'get' or 'fetch', placing it in the Read category with low severity.
From the tool's definition Tool returns a single example 'by name' with its 'query and compiled SQL preview' — a retrieval operation with no modification, deletion, or execution of queries against live data.
Attacks that exploit this kind of access
Get a single example by name with its query and compiled SQL preview. 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 get_example: 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.
get_example 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_example 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_example. 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_example 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 →