[Developer tool] Register a new app on the tru platform. This tool handles authentication and registration in one step — no separate login call needed. It opens a browser where the developer confirms their tru account, registers the app, and lands on the setup page. Before calling, explore the co...
AI agents use dev_register_app 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 |
|---|---|---|---|
website | string | — | The app's public URL. Required for API discovery (dev_generate_skill) and agent signup. Always ask the developer for this. |
description | string | — | One-line description of what the app does |
display_name | string | Yes | Human-friendly display name for the app |
service_name | string | Yes | Lowercase slug for the app (letters, numbers, hyphens). Must be unique. |
provision_url | string | — | URL of your provision endpoint. tru POSTs { email, name, tru_user_id } here to auto-create accounts for tru users. |
redirect_uris | array | — | OAuth redirect URIs for login. Look for auth callback routes in the codebase (e.g. /api/auth/callback/tru) and include the full URL. This is required for the OA |
allowed_fields | array | — | Credential fields this app can request (e.g. ['name', 'email', 'phone']) |
Parameters from the server's own tool schema.
The tool creates new applications and generates authentication credentials (API key, app secret), which are reversible actions that modify platform state. This is a Write operation rather than Execute because it doesn't run arbitrary code—it performs a structured registration action.
From the tool's definition Register a new app on the tru platform. This tool handles authentication and registration in one step... Returns an API key, an app secret. The tool creates new application records and generates credentials.
Attacks that exploit this kind of access
[Developer tool] Register a new app on the tru platform. This tool handles authentication and registration in one step — no separate login call needed. It opens a browser where the developer confirms their tru account, registers the app, and lands on the setup page. Before calling, explore the codebase — package.json, README, docs, marketing pages, source code, config files — to auto-fill service_name, display_name, description, website, and redirect_uris. Propose values to the developer for confirmation rather than asking them to fill things in. Returns an API key, an app secret, and automatically configures the API key for this session and saves it to .mcp.json. After registration, run dev_connect_stripe to link the developer's Stripe account. All subsequent tru tools use the API key automatically. 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_register_app accepts 7 parameters: website, description, display_name, service_name, provision_url, redirect_uris, allowed_fields. Required: display_name, 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_register_app: 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_register_app 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_register_app 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_register_app. 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_register_app 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 →