Update table configuration
AI agents use update_table_config to create or update resources in StarTree MCP Server for Apache Pinot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your StarTree MCP Server for Apache Pinot environment.
This tool modifies table configuration settings, which are reversible changes (configurations can be updated again). It does not delete data or execute arbitrary code. However, the severity is high because misconfigured table settings could impact data ingestion, query performance, or system stability.
From the tool's definition Tool name 'update_table_config' and description 'Update table configuration' indicate modification of existing table settings in Apache Pinot. The verb 'update' clearly signals a write operation that alters configuration state.
Documented attack patterns abuse exactly the kind of access update_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 update_table_config:
{
"version": "1",
"default": "deny",
"tools": {
"update_table_config": {
"limits": [
{
"counter": "update_table_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_table_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update table configuration. It is categorised as a Write tool in the StarTree MCP Server for Apache Pinot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the StarTree MCP Server for Apache Pinot MCP server in PolicyLayer and add a rule for update_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.
update_table_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.