dev_set_provision_url

Register the app's provision endpoint URL with tru. tru POSTs { email, name, tru_user_id, purchases } to this URL to auto-create accounts for verified users. This is how tru connects user identity and payments to your app's account system. Required for the provisioning phase of setup.

Server Tru tru-mcp
Category Write
Risk class Medium
Parameters 11 required

What dev_set_provision_url does on Tru

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

ParameterTypeRequiredDescription
provision_url string Yes The URL of the app's provision endpoint (e.g. https://myapp.com/api/tru/provision or http://localhost:4000/api/tru/provision for local dev).

Parameters from the server's own tool schema.

Why dev_set_provision_url needs a policy

The tool creates or modifies configuration (registering a provisioning endpoint URL) that directly affects account creation workflows. While it doesn't directly delete data or move money, it sets up the mechanism by which user accounts and billing relationships are established.

From the tool's definition Tool description states it 'Register[s] the app's provision endpoint URL' and enables tru to 'auto-create accounts for verified users' by POSTing user identity and payment data.

Questions about dev_set_provision_url

What does the dev_set_provision_url tool do? +

Register the app's provision endpoint URL with tru. tru POSTs { email, name, tru_user_id, purchases } to this URL to auto-create accounts for verified users. This is how tru connects user identity and payments to your app's account system. Required for the provisioning phase of setup. 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.

What parameters does dev_set_provision_url accept? +

dev_set_provision_url accepts 1 parameter: provision_url. Required: provision_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dev_set_provision_url? +

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

What risk level is dev_set_provision_url? +

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

Can I rate-limit dev_set_provision_url? +

Yes. Add a rate_limit block to the dev_set_provision_url 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 dev_set_provision_url completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.