dev_send_setup_report · Tru MCP: Risk & Policy

WHAT IT DOES

What dev_send_setup_report does on Tru

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

WHY IT NEEDS A POLICY

Why dev_send_setup_report needs a policy

This tool creates and sends an email (a write operation with side effects), but the side effect is informational and reversible—an email can be recalled or marked as spam without cascading consequences. It does not execute arbitrary code, delete data, move money, or perform destructive operations. Severity is low because misuse would result in unwanted setup emails to developers, which is annoying but not damaging.

From the tool's definition Tool name 'dev_send_setup_report' and description 'Send a setup summary email' indicates the tool sends/writes an email message. It modifies state by recording that a setup report was sent.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dev_send_setup_report Rate-limited

dev_send_setup_report stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dev_send_setup_report": {
      "limits": [
        {
          "counter": "dev_send_setup_report_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tru, so you can run agents against it safely.

FAQ

Questions about dev_send_setup_report

What does the dev_send_setup_report tool do? +

Send a setup summary email to the developer after completing the tru setup flow. Includes app details, API key prefix, key links, and setup progress. 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.

How do I enforce a policy on dev_send_setup_report? +

Register the Tru MCP server in PolicyLayer and add a rule for dev_send_setup_report: 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_send_setup_report? +

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

Can I rate-limit dev_send_setup_report? +

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

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

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