create_tenant_provider_policy · UseGrant MCP Server MCP

WHAT IT DOES

What create_tenant_provider_policy does on UseGrant MCP Server

AI agents use create_tenant_provider_policy 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.

WHY IT NEEDS A POLICY

Why create_tenant_provider_policy needs a policy

Creating a policy is a reversible write operation that modifies configuration state in the UseGrant platform. While it affects security posture and access control (raising severity above low), it is not irreversible (not Destructive), does not execute arbitrary code (not Execute), and does not directly move money (not Financial).

From the tool's definition Tool name and description indicate creation of a new policy ('create' + 'policy'). The sibling tools include destructive operations (delete_*) and access control operations (create_access_token, create_client), establishing this as an access management system…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_tenant_provider_policy Rate-limited

create_tenant_provider_policy 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_tenant_provider_policy": {
      "limits": [
        {
          "counter": "create_tenant_provider_policy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UseGrant MCP Server, so you can run agents against it safely.

FAQ

Questions about create_tenant_provider_policy

What does the create_tenant_provider_policy tool do? +

Create a new policy for a tenant provider. 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.

How do I enforce a policy on create_tenant_provider_policy? +

Register the UseGrant MCP Server MCP server in PolicyLayer and add a rule for create_tenant_provider_policy: 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.

What risk level is create_tenant_provider_policy? +

create_tenant_provider_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_tenant_provider_policy? +

Yes. Add a rate_limit block to the create_tenant_provider_policy 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.

How do I block create_tenant_provider_policy completely? +

Set action: deny in the PolicyLayer policy for create_tenant_provider_policy. 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.

What MCP server provides create_tenant_provider_policy? +

create_tenant_provider_policy 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.