Create a new tenant
AI agents use create_tenant to create or update resources in UseGrant MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UseGrant MCP Server environment.
This tool creates a new tenant entity in the UseGrant platform, which is a reversible write operation. It modifies system state by adding a new tenant record but does not delete data or execute arbitrary code. The severity is medium because creating tenants could have downstream effects on access control and resource allocation, but the action itself is not destructive or immediately damaging.
From the tool's definition Tool name is 'create_tenant' and description states 'Create a new tenant'. This is a creation action that adds a new entity to the system.
Attacks that exploit this kind of access
Create a new tenant. It is categorised as a Write tool in the UseGrant MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UseGrant 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 UseGrant 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 UseGrant MCP Server MCP server (usegranthq/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →