Returns focused setup instructions for a specific phase of the tru integration guide. Call with phase number (1-4) for step-by-step instructions, or "status" to see completion progress. Phases: 1=Register, 2=Payments, 3=Provisioning, 4=Go Live.
AI agents call dev_setup_guide 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 |
|---|---|---|---|
section | object | Yes | Phase number (1-4) or "status" to see completion progress |
Parameters from the server's own tool schema.
The tool only reads and returns setup guide content or status information. It does not modify, execute, or delete anything. It is essentially a documentation retrieval tool that returns text instructions based on a phase parameter.
From the tool's definition 'Returns focused setup instructions for a specific phase' and 'see completion progress' — purely retrieves documentation/instructions with no side effects
Attacks that exploit this kind of access
Returns focused setup instructions for a specific phase of the tru integration guide. Call with phase number (1-4) for step-by-step instructions, or "status" to see completion progress. Phases: 1=Register, 2=Payments, 3=Provisioning, 4=Go Live. It is categorised as a Read tool in the Tru MCP Server, which means it retrieves data without modifying state.
dev_setup_guide accepts 1 parameter: section. Required: section. 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_setup_guide: 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_setup_guide 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_setup_guide 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_setup_guide. 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_setup_guide 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 →