AI agents use update_schema 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.
The tool modifies existing data structures (schemas) but does not delete them irreversibly or execute arbitrary code. Schema updates are Write operations - they change configuration state reversibly. Severity is medium because incorrect schema modifications could impact data ingestion or query correctness across the Pinot cluster, but the effect is typically recoverable through a schema downgrade or correction.
From the tool's definition Tool name is 'update_schema' and description states 'Update an existing schema'. This directly modifies schema metadata in Apache Pinot, which is a reversible operation.
Documented attack patterns abuse exactly the kind of access update_schema 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_schema:
{
"version": "1",
"default": "deny",
"tools": {
"update_schema": {
"limits": [
{
"counter": "update_schema_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_schema 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 an existing schema. 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_schema: 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_schema 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_schema 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_schema. 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_schema 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.