AI agents use create_tenant to create or update resources in WeKnora MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WeKnora MCP Server environment.
This tool creates a new tenant, which is a reversible operation (tenants can be deleted or modified). However, creating tenants may grant access to sensitive multi-tenant infrastructure and resources, affecting system configuration and potentially enabling unauthorized users to establish isolated environments.
From the tool's definition Tool name 'create_tenant' and description 'Create a new tenant in WeKnora' indicate creation of a new organizational entity within 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 WeKnora MCP Server, 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.
Create a new tenant in WeKnora. It is categorised as a Write tool in the WeKnora MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WeKnora MCP Server 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 WeKnora MCP Server. 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 WeKnora MCP Server MCP server (nannaolympicbroadcast/weknoramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WeKnora MCP Server, 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.
21 WeKnora MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.