Get the pre-loaded OBML YAML model source.
AI agents call get_model 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 tool retrieves or queries data (the OBML YAML model source) without side effects. It does not create, modify, execute, delete, or move money. Classification as Read is appropriate. Severity is low because retrieving a model definition poses minimal risk even if accessed by an unauthorized agent; the worst case is information disclosure of the schema/structure itself, not data exfiltration or system compromise.
From the tool's definition Tool name is 'get_model' and description states 'Get the pre-loaded OBML YAML model source' — a retrieval operation with no modification, execution, or deletion capabilities.
Attacks that exploit this kind of access
Get the pre-loaded OBML YAML model source. 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_model: 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_model 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_model 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_model. 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_model 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 →