Provision a new user or update an existing one in /users/. Creates user record, auto-generates developer/stakeholder IDs, and assigns projects. Idempotent: safe to re-run.
AI agents use provision_user to create or update resources in Planning Game — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planning Game environment.
This tool creates or updates user records, assigns IDs, and assigns projects. It is a Write operation (create/update) rather than Destructive since it is idempotent and does not delete data. Severity is high because user provisioning and project assignment can affect access control, permissions, and project membership across the system — misuse could grant unauthorized access or disrupt team assignments.
From the tool's definition Provision a new user or update an existing one in /users/. Creates user record, auto-generates developer/stakeholder IDs, and assigns projects. Idempotent: safe to re-run.
Attacks that exploit this kind of access
Provision a new user or update an existing one in /users/. Creates user record, auto-generates developer/stakeholder IDs, and assigns projects. Idempotent: safe to re-run. It is categorised as a Write tool in the Planning Game MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Planning Game MCP server in PolicyLayer and add a rule for provision_user: 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 Planning Game. Nothing to install.
provision_user 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 provision_user 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 provision_user. 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.
provision_user is provided by the Planning Game MCP server (planning-game-mcp). 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 →