reset-table-segments

THE RISK

Critical Risk

Why reset-table-segments needs a policy

Resetting table segments in Apache Pinot affects the availability and integrity of data stored in those segments. While not a direct deletion, the reset operation (disable->wait->enable) is a state transition that could result in data loss, segment corruption, or prolonged unavailability.

From the tool's definition Tool name 'reset-table-segments' combined with description 'Resets segments for a table' indicates irreversible segment state management.

Documented attack patterns abuse exactly the kind of access reset-table-segments gives an agent:

POLICY

How to control reset-table-segments

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 reset-table-segments:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset-table-segments"
  ]
}

reset-table-segments disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More StarTree MCP Server for Apache Pinot tools

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 Write add-index Adds a specified index type to one or more columns in a table

All 26 StarTree MCP Server for Apache Pinot tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in StarTree MCP Server for Apache Pinot → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about reset-table-segments

What does the reset-table-segments tool do? +

Resets segments for a table (disable->wait->enable). Use. It is categorised as a Destructive tool in the StarTree MCP Server for Apache Pinot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset-table-segments? +

Register the StarTree MCP Server for Apache Pinot MCP server in PolicyLayer and add a rule for reset-table-segments: 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 reset-table-segments? +

reset-table-segments is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset-table-segments? +

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

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

reset-table-segments 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 →