AI agents use create_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.
This tool creates a new schema, which is a reversible data modification operation. It does not delete or destroy data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial). Schema creation can be undone by deletion, and the impact is scoped to schema management rather than data deletion.
From the tool's definition Tool name is 'create_schema' and description states 'Create a new schema'. The verb 'create' indicates it generates new data structures within the Apache Pinot system.
Documented attack patterns abuse exactly the kind of access create_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 create_schema:
{
"version": "1",
"default": "deny",
"tools": {
"create_schema": {
"limits": [
{
"counter": "create_schema_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_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.
Create a new 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 create_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.
create_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 create_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 create_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.
create_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.