AI agents call get_table_config 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.
This tool retrieves table configuration information from Apache Pinot without modifying, executing, or deleting any data. It is a pure read operation with no destructive capability or external side effects. The low severity reflects that exposing table configuration poses minimal risk—it is metadata that is typically not sensitive in nature within a Pinot cluster context.
From the tool's definition Tool name 'get_table_config' and description 'Get table configuration' indicate retrieval of existing configuration data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_table_config gives an agent:
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 get_table_config:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_config": {}
}
} get_table_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get table configuration. 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.
Register the StarTree MCP Server for Apache Pinot MCP server in PolicyLayer and add a rule for get_table_config: 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.
get_table_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_table_config 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 get_table_config. 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.
get_table_config 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.
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.
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.