Get the OBML format reference.
AI agents call get_obml_reference 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 static reference documentation without side effects. It fits the 'Read' category as a get/fetch operation. Severity is low because misuse cannot cause harm—an AI requesting reference material has minimal blast radius. The confidence is high based on clear read-only semantics, though the terse description provides limited detail.
From the tool's definition Tool name 'get_obml_reference' and description 'Get the OBML format reference' indicate a retrieval operation that returns documentation or reference material about the OBML (OrionBelt Markup Language) format. No modification, execution, or deletion occurs.
Attacks that exploit this kind of access
Get the OBML format reference. 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_obml_reference: 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_obml_reference 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_obml_reference 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_obml_reference. 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_obml_reference 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 →