This record as markdown: /tools/frontmcp/get-auth-info.md
What get-auth-info does on Frontmcp
AI agents call get-auth-info to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-auth-info is rated Low
This tool retrieves authentication context information, which is a read-only operation. However, severity is elevated to 'medium' rather than 'low' because auth context may contain sensitive information (tokens, session IDs, user identifiers, permissions) that could be misused if exposed to an AI agent without proper access controls, even though the tool itself performs no destructive or executable actions.
From the tool's definition Tool name 'get-auth-info' and description 'Returns current auth context (for testing)' indicate a retrieval operation that queries authentication state without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get-auth-info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-auth-info, this is the rule to start with:
get-auth-info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every get-auth-info call is checked against it from then on.
Questions about get-auth-info
Returns current auth context (for testing). It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for get-auth-info: 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 Frontmcp. Nothing to install.
get-auth-info 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 get-auth-info 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 get-auth-info. 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.
get-auth-info is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue