Remove a property from an entity type.
AI agents call remove_property to permanently remove resources in Fabric Ontology MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the blast radius is scoped to ontology metadata rather than data deletion, removing a property from an entity type is a destructive action that alters the schema/structure and cannot be trivially reversed. This is categorized as Destructive rather than Write because property removal is an irreversible structural change to the ontology, not a reversible update.
From the tool's definition Tool named 'remove_property' with description 'Remove a property from an entity type' indicates deletion of ontology metadata. The server description confirms 'full CRUD control' including ability to modify entity types.
Documented attack patterns abuse exactly the kind of access remove_property 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 remove_property:
{
"version": "1",
"default": "deny",
"hide": [
"remove_property"
]
} remove_property disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a property from an entity type. It is categorised as a Destructive tool in the Fabric Ontology MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fabric Ontology MCP Server MCP server in PolicyLayer and add a rule for remove_property: 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.
remove_property is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_property 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 remove_property. 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.
remove_property 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.