auth_settings · Run402 MCP: Risk & Policy

WHAT IT DOES

What auth_settings does on Run402

AI agents use auth_settings to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.

WHY IT NEEDS A POLICY

Why auth_settings needs a policy

This tool modifies authentication and authorization settings for a project, which are critical security configurations. While changes are reversible (Write, not Destructive), misconfiguration could grant unauthorized access or weaken security controls, affecting all project users.

From the tool's definition Tool name 'auth_settings' combined with description 'Update project auth settings' indicates modification of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth_settings Rate-limited

auth_settings 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": {
    "auth_settings": {
      "limits": [
        {
          "counter": "auth_settings_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 Run402, so you can run agents against it safely.

FAQ

Questions about auth_settings

What does the auth_settings tool do? +

Update project auth settings: allow_password_set, preferred_sign_in_method, public_signup, and require_passkey_for_project_admin. Requires service_key. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on auth_settings? +

Register the Run402 MCP server in PolicyLayer and add a rule for auth_settings: 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 Run402. Nothing to install.

What risk level is auth_settings? +

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

Can I rate-limit auth_settings? +

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

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

auth_settings is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.