AI agents use dev_update_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 | — | App's public URL |
description | string | — | One-line description |
display_name | string | — | Display name |
support_email | string | — | Public support email shown on app profile |
free_trial_cents | number | — | Number of free requests for new user trials (0 = no trial) |
auto_upgrade_enabled | boolean | — | Enable auto-upgrade: suggest subscription plans when per-request spend exceeds plan price |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly by updating app settings. It does not delete data (which would be Destructive), does not move money (which would be Financial), and does not execute arbitrary code (which would be Execute).
From the tool's definition Tool description states 'Update app settings on tru' and lists modifiable fields: support_email, website, description, display_name, or auto_upgrade_enabled. These are reversible modifications to application configuration.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Update app settings on tru. Use this to set support_email, website, description, display_name, or auto_upgrade_enabled. Works with the app's API key — no admin key needed. 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_update_app accepts 6 parameters: website, description, display_name, support_email, free_trial_cents, auto_upgrade_enabled. 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_update_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_update_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_update_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_update_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_update_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 →