Provision a tru user on a third-party app. The app must have a provision_url configured. tru sends the user's verified identity to the app's provision endpoint, the app creates an account and returns credentials (API key, account ID, etc.), and tru stores them. Returns the credentials so the agen...
AI agents use dev_provision_user to create or update resources in Tru — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tru environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Email address of the tru user to provision |
service_name | string | Yes | The service_name of the app to provision the user on |
Parameters from the server's own tool schema.
The tool creates new user accounts on third-party applications and stores credentials. While account creation is theoretically reversible (unlike deletion), it modifies system state by adding new identities and authentication material to external systems, and the stored credentials represent a persistent, non-trivial change.
From the tool's definition "Provision a tru user on a third-party app" and "the app creates an account and returns credentials (API key, account ID, etc.), and tru stores them." This action creates new accounts and stores credentials irreversibly.
Attacks that exploit this kind of access
Provision a tru user on a third-party app. The app must have a provision_url configured. tru sends the user's verified identity to the app's provision endpoint, the app creates an account and returns credentials (API key, account ID, etc.), and tru stores them. Returns the credentials so the agent can use the service immediately. If the user was already provisioned, returns the stored credentials without hitting the app again. It is categorised as a Write tool in the Tru MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dev_provision_user accepts 2 parameters: email, service_name. Required: email, service_name. The full parameter table on this page comes from the server's own tool schema.
Register the Tru MCP server in PolicyLayer and add a rule for dev_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 Tru. Nothing to install.
dev_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 dev_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 dev_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.
dev_provision_user is provided by the Tru MCP server (tru-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 →