Validate an app's tru integration. Checks platform config (registration, Stripe), verifies tru() returns 402 on unauthenticated requests, confirms API key auth passes through, and returns a checklist with pass/fail per check and actionable fixes for failures.
AI agents call dev_validate to retrieve information from Tru without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
scope | string | — | Validation scope: 'provision' checks only app registration, Stripe, provision endpoint, and charge creation. 'full' (default) also checks discovery files and fr |
service_name | string | — | Service name of the app to validate. Defaults to the stored app from config. |
Parameters from the server's own tool schema.
The tool performs validation and verification checks — reading configuration state, testing API responses, and returning a checklist. It does not modify, create, delete, or execute code/commands. All described actions are diagnostic/read-only in nature.
From the tool's definition Validate an app's tru integration. Checks platform config (registration, Stripe), verifies tru() returns 402 on unauthenticated requests, confirms API key auth passes through, and returns a checklist with pass/fail per check and actionable fixes for failures.
Attacks that exploit this kind of access
Validate an app's tru integration. Checks platform config (registration, Stripe), verifies tru() returns 402 on unauthenticated requests, confirms API key auth passes through, and returns a checklist with pass/fail per check and actionable fixes for failures. It is categorised as a Read tool in the Tru MCP Server, which means it retrieves data without modifying state.
dev_validate accepts 2 parameters: scope, 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_validate: 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_validate is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dev_validate 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_validate. 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_validate 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 →