AI agents use add_contextualization 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.
The tool name 'add_contextualization' suggests creating or attaching contextual information to ontology items, consistent with the server's CRUD capabilities. The empty description reduces confidence, but the naming pattern and sibling tools (add_data_binding, add_entity_type, add_property, add_relationship_type) strongly indicate a Write operation that modifies ontology state.
From the tool's definition Tool named 'add_contextualization' with empty description; sibling tools on this server are CRUD operations (add_*, create_*, delete_*), indicating this tool likely adds or modifies ontology metadata in Microsoft Fabric.
Documented attack patterns abuse exactly the kind of access add_contextualization 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 add_contextualization:
{
"version": "1",
"default": "deny",
"tools": {
"add_contextualization": {
"limits": [
{
"counter": "add_contextualization_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_contextualization 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.
add_contextualization. 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 add_contextualization: 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.
add_contextualization 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 add_contextualization 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 add_contextualization. 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.
add_contextualization 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.