Creates a new tenant in the specified database
AI agents use create-tenant to create or update resources in Nile — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nile environment.
This tool creates a new tenant, which is a persistent data structure modification. It is Write (not Destructive) because tenant creation is reversible via delete-tenant. It is Write (not Execute) because it modifies a specific, predictable data structure rather than running arbitrary code.
From the tool's definition Tool name: create-tenant. Description: "Creates a new tenant in the specified database" — the verb 'Creates' indicates irreversible addition of a new entity to the system.
Documented attack patterns abuse exactly the kind of access create-tenant gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nile, and nothing reaches the server without passing your rules. This is the rule we recommend for create-tenant:
{
"version": "1",
"default": "deny",
"tools": {
"create-tenant": {
"limits": [
{
"counter": "create-tenant_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-tenant 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.
Creates a new tenant in the specified database. It is categorised as a Write tool in the Nile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nile MCP server in PolicyLayer and add a rule for create-tenant: 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 Nile. Nothing to install.
create-tenant 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-tenant 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-tenant. 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-tenant is provided by the Nile MCP server (@niledatabase/nile-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nile, 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.
11 Nile tools catalogued and risk-classified — across an index of 43,000+ MCP servers.