Low Risk

profile_kql_table

profile_kql_table

How to control profile_kql_table ↓

What profile_kql_table does on Fabric Ontology MCP Server

AI agents call profile_kql_table to retrieve information from Fabric Ontology MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why profile_kql_table needs a policy

The name implies a read/analysis operation (profiling) against a KQL table. Profiling typically involves querying data to gather statistics or metadata, placing it in the Read category. However, the empty description reduces confidence — it could potentially execute arbitrary KQL queries. Severity is medium because KQL tables may contain sensitive data and profiling could expose it.

From the tool's definition Tool name 'profile_kql_table' suggests reading/profiling a KQL (Kusto Query Language) table — no description provided.

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

How to control profile_kql_table

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "profile_kql_table": {}
  }
}

profile_kql_table is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about profile_kql_table

What does the profile_kql_table tool do? +

profile_kql_table. It is categorised as a Read tool in the Fabric Ontology MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on profile_kql_table? +

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

profile_kql_table is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit profile_kql_table? +

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

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

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

Free to start. No card required.

45 Fabric Ontology MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.