list_examples
AI agents call list_examples 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 name indicates retrieval of examples without modification or execution capabilities. No description is available to contradict this inference. Even in an MCP analytics context where data retrieval poses minimal risk, the low confidence reflects the absent description. Classified as Read with low severity due to its informational nature and lack of side effects.
From the tool's definition Tool name 'list_examples' follows a Read pattern (list/get operations); description is empty, limiting confidence. Sibling tools like 'get_example' and 'describe_model' are clearly Read operations, suggesting consistent data retrieval behavior.
Attacks that exploit this kind of access
list_examples. 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_examples: 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_examples 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_examples 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_examples. 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_examples 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 →