tableconfig_schema_details

WHAT IT DOES

What tableconfig_schema_details does on StarTree MCP Server for Apache Pinot

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

THE RISK

Low Risk

Why tableconfig_schema_details needs a policy

This tool retrieves metadata about table configuration and schema in Apache Pinot. It performs a query operation to fetch existing data with no side effects, no data modification, no code execution, and no destructive operations. This is a straightforward read operation with minimal security risk—the blast radius of misuse is limited to information disclosure of database schema and configuration details.

From the tool's definition Tool name 'tableconfig_schema_details' and description 'Get table config and schema' indicate data retrieval operations.

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

POLICY

How to control tableconfig_schema_details

PolicyLayer is an MCP gateway — it sits between your AI agents and StarTree MCP Server for Apache Pinot, and nothing reaches the server without passing your rules. This is the rule we recommend for tableconfig_schema_details:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tableconfig_schema_details": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More StarTree MCP Server for Apache Pinot tools

Destructive reset-table-segments Resets segments for a table (disable->wait->enable). Use Execute force_commit Force commit the current consuming segments Execute pause_consumption Pause consumption of a realtime table Execute read_query Execute a SELECT query on the Pinot database Execute rebalance-table Rebalances a table (reassign instances and segments) Execute reload_table_filters reload_table_filters Execute reload-table-segments Reload all segments for a table (applies config changes, can Execute resume_consumption Resume consumption of a realtime table

All 26 StarTree MCP Server for Apache Pinot tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about tableconfig_schema_details

What does the tableconfig_schema_details tool do? +

Get table config and schema. It is categorised as a Read tool in the StarTree MCP Server for Apache Pinot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tableconfig_schema_details? +

Register the StarTree MCP Server for Apache Pinot MCP server in PolicyLayer and add a rule for tableconfig_schema_details: 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 StarTree MCP Server for Apache Pinot. Nothing to install.

What risk level is tableconfig_schema_details? +

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

Can I rate-limit tableconfig_schema_details? +

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

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

tableconfig_schema_details is provided by the StarTree MCP Server for Apache Pinot MCP server (startreedata/mcp-pinot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every StarTree MCP Server for Apache Pinot tool call.

Start from StarTree MCP Server for Apache Pinot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

26 StarTree MCP Server for Apache Pinot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.