export_model_to_osi · Orionbelt Semantic Layer MCP

WHAT IT DOES

What export_model_to_osi does on Orionbelt Semantic Layer

AI agents use export_model_to_osi to create or update resources in Orionbelt Semantic Layer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Orionbelt Semantic Layer environment.

WHY IT NEEDS A POLICY

Why export_model_to_osi needs a policy

The tool name suggests exporting a semantic model to OSI (likely Open Standards Initiative or similar format), which constitutes data creation/modification. While not irreversible (Write rather than Destructive), this could expose or duplicate governed semantic models to external formats. The lack of description lowers confidence.

From the tool's definition Tool name 'export_model_to_osi' indicates exporting/writing model data to OSI format. No description provided, but 'export' operations typically create new artifacts or files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_model_to_osi Rate-limited

export_model_to_osi stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_model_to_osi": {
      "limits": [
        {
          "counter": "export_model_to_osi_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Orionbelt Semantic Layer, so you can run agents against it safely.

FAQ

Questions about export_model_to_osi

What does the export_model_to_osi tool do? +

export_model_to_osi. It is categorised as a Write tool in the Orionbelt Semantic Layer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_model_to_osi? +

Register the Orionbelt Semantic Layer MCP server in PolicyLayer and add a rule for export_model_to_osi: 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.

What risk level is export_model_to_osi? +

export_model_to_osi is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_model_to_osi? +

Yes. Add a rate_limit block to the export_model_to_osi 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.

How do I block export_model_to_osi completely? +

Set action: deny in the PolicyLayer policy for export_model_to_osi. 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.

What MCP server provides export_model_to_osi? +

export_model_to_osi 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.