Rebalances a table (reassign instances and segments)
AI agents invoke rebalance-table to trigger actions in StarTree MCP Server for Apache Pinot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Rebalancing a table involves reassigning instances and segments across the cluster, which is an operational action that triggers external operations and can significantly impact cluster performance and data availability. It is not a simple read or write, but an execution of a complex operational procedure.
From the tool's definition Rebalances a table (reassign instances and segments)
Documented attack patterns abuse exactly the kind of access rebalance-table 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 rebalance-table:
{
"version": "1",
"default": "deny",
"tools": {
"rebalance-table": {
"limits": [
{
"counter": "rebalance-table_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} rebalance-table stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Rebalances a table (reassign instances and segments). It is categorised as a Execute tool in the StarTree MCP Server for Apache Pinot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the StarTree MCP Server for Apache Pinot MCP server in PolicyLayer and add a rule for rebalance-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 StarTree MCP Server for Apache Pinot. Nothing to install.
rebalance-table is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rebalance-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.
Set action: deny in the PolicyLayer policy for rebalance-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.
rebalance-table 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.