test_security · Better Auth MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_security does on Better Auth MCP Server

AI agents invoke test_security to trigger actions in Better Auth MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why test_security needs a policy

This tool runs active security tests against an authentication system. While described as 'tests', executing security probes against an auth system can trigger real operations, modify state, lock accounts, generate alerts, or cause disruptions.

From the tool's definition "Run security tests" - actively executes test operations against the authentication setup

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_security Rate-limited

test_security stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_security": {
      "limits": [
        {
          "counter": "test_security_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about test_security

What does the test_security tool do? +

Run security tests on Better-Auth setup. It is categorised as a Execute tool in the Better Auth MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_security? +

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

What risk level is test_security? +

test_security is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_security? +

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

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

test_security is provided by the Better Auth MCP Server MCP server (lexiconalex/better-auth-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

test_security is one line of Better Auth MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →