Create a new ontology in a workspace.
AI agents use create_ontology to create or update resources in Fabric Ontology MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fabric Ontology MCP Server environment.
Creating an ontology generates new data structures and metadata in Microsoft Fabric workspaces. This is a reversible write operation—ontologies can be updated or deleted later. While it modifies the workspace state, it does not execute arbitrary code, delete existing data, or involve financial transactions.
From the tool's definition Tool description states 'Create a new ontology in a workspace,' which is a create operation that adds new data structures to Fabric. The server description confirms 'full CRUD control' including create operations on ontology items.
Documented attack patterns abuse exactly the kind of access create_ontology gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fabric Ontology MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_ontology:
{
"version": "1",
"default": "deny",
"tools": {
"create_ontology": {
"limits": [
{
"counter": "create_ontology_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_ontology 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.
Free to start. No card required.
Create a new ontology in a workspace. It is categorised as a Write tool in the Fabric Ontology MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fabric Ontology MCP Server MCP server in PolicyLayer and add a rule for create_ontology: 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 Fabric Ontology MCP Server. Nothing to install.
create_ontology is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_ontology 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 create_ontology. 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.
create_ontology is provided by the Fabric Ontology MCP Server MCP server (tmdaidevs/ontology-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fabric Ontology MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 Fabric Ontology MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.