Get full auth system overview: guard hierarchy, session flow, Better Auth setup, roles, and decorator system.
AI agents call auth_get_overview to retrieve information from LaunchFrame MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing authentication system configuration and structure (guard hierarchy, session flow, roles, decorator system). It is purely informational retrieval with no side effects, state changes, or code execution. It falls clearly under the Read category.
From the tool's definition Tool name includes 'get' and description states 'Get full auth system overview' — retrieves architectural information about the authentication system without modifying or executing anything.
Attacks that exploit this kind of access
Get full auth system overview: guard hierarchy, session flow, Better Auth setup, roles, and decorator system. It is categorised as a Read tool in the LaunchFrame MCP MCP Server, which means it retrieves data without modifying state.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for auth_get_overview: 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 LaunchFrame MCP. Nothing to install.
auth_get_overview 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 auth_get_overview 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 auth_get_overview. 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.
auth_get_overview is provided by the LaunchFrame MCP server (launchframe-dev/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 →