remove_data_binding

THE RISK

Critical Risk

Why remove_data_binding needs a policy

Removing a data binding disconnects an entity type from its underlying data source in the ontology. This is a destructive, non-reversible operation (there is no 'undo' implied), and misuse could break data pipelines, queries, or downstream applications relying on that binding. Severity is high given the blast radius across any consumers of the affected entity type.

From the tool's definition 'Remove a data binding from an entity type' — removal of a binding is an irreversible deletion of a configuration link between an entity type and its data source.

Documented attack patterns abuse exactly the kind of access remove_data_binding gives an agent:

POLICY

How to control remove_data_binding

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_data_binding:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_data_binding"
  ]
}

remove_data_binding disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Fabric Ontology MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Fabric Ontology MCP Server tools

Destructive delete_ontology Delete an ontology. Destructive remove_contextualization Remove a contextualization from a relationship type. Destructive remove_document Remove a document from an entity type by its URL. Destructive remove_entity_type Remove an entity type from an ontology. Destructive remove_property Remove a property from an entity type. Destructive remove_relationship_type Remove a relationship type from an ontology. Write add_contextualization add_contextualization Write add_data_binding add_data_binding

All 45 Fabric Ontology MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Fabric Ontology MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_data_binding

What does the remove_data_binding tool do? +

Remove a data binding 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.

How do I enforce a policy on remove_data_binding? +

Register the Fabric Ontology MCP Server MCP server in PolicyLayer and add a rule for remove_data_binding: 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.

What risk level is remove_data_binding? +

remove_data_binding is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_data_binding? +

Yes. Add a rate_limit block to the remove_data_binding 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 remove_data_binding completely? +

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

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

Enforce policy on every Fabric Ontology MCP Server tool call.

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.

CHECK YOUR STACK →