dev_configure_login · Tru MCP: Risk & Policy

WHAT IT DOES

What dev_configure_login does on Tru

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

PARAMETERS

Parameter	Type	Required	Description
`service_name`	string	Yes	The service_name of the app to initiate OAuth for

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why dev_configure_login needs a policy

An AI agent can call dev_configure_login faster than any human can review — one bad instruction and it creates or modifies resources in Tru by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dev_configure_login Rate-limited

dev_configure_login 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_configure_login": {
      "limits": [
        {
          "counter": "dev_configure_login_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_configure_login

What does the dev_configure_login tool do? +

Generate an OAuth authorization URL for a tru-integrated app. Given a service_name, looks up the app and returns the URL the user should open in their browser to authenticate via tru. NOTE: For web apps using tru.js, the simpler approach is <tru-login-button redirect-uri='/login'> — the SDK redirects to tru, the user authenticates, and is redirected back with a signed JWT in the URL fragment. Call tru.handleCallback() on the return page to extract the token. This tool generates URLs for the classic OAuth code flow. 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.

What parameters does dev_configure_login accept? +

dev_configure_login accepts 1 parameter: service_name. Required: service_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dev_configure_login? +

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

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

Can I rate-limit dev_configure_login? +

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

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

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