Check the current authentication status and mode of the MCP Server and also returns the current graph permission scopes of the access token for the current session.
AI agents call get-auth-status to retrieve information from Lokka (Microsoft 365 MCP server) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves authentication status and permission information without modifying any resources. It is purely informational—checking status and returning scopes are read-only operations. No data is created, modified, deleted, or executed. Severity is low because the information returned, while sensitive, does not enable direct harmful actions without further tool use.
From the tool's definition Tool name 'get-auth-status' and description 'Check the current authentication status and mode' and 'returns the current graph permission scopes' indicate query/retrieval operations with no side effects.
Documented attack patterns abuse exactly the kind of access get-auth-status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lokka (Microsoft 365 MCP server), and nothing reaches the server without passing your rules. This is the rule we recommend for get-auth-status:
{
"version": "1",
"default": "deny",
"tools": {
"get-auth-status": {}
}
}get-auth-status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the current authentication status and mode of the MCP Server and also returns the current graph permission scopes of the access token for the current session. It is categorised as a Read tool in the Lokka (Microsoft 365 MCP server) MCP Server, which means it retrieves data without modifying state.
Register the Lokka (Microsoft 365 MCP server) MCP server in PolicyLayer and add a rule for get-auth-status: 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 Lokka (Microsoft 365 MCP server). Nothing to install.
get-auth-status 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-status 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-status. 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-status is provided by the Lokka (Microsoft 365 MCP server) MCP server (merill/lokka). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lokka (Microsoft 365 MCP server), add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Lokka (Microsoft 365 MCP server) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.