Check the current SharePoint authentication status
AI agents call check_auth_status to retrieve information from SharePoint MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely queries and returns the current authentication status. It has no side effects, does not execute operations, does not modify data, and does not delete anything. It is a simple read operation typical of status-checking utilities. The low severity reflects minimal risk if misused, as it only reveals whether authentication is valid and poses no blast radius for unintended data modification or loss.
From the tool's definition Tool name 'check_auth_status' and description 'Check the current SharePoint authentication status' indicate a query operation that retrieves authentication state without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Check the current SharePoint authentication status. It is categorised as a Read tool in the SharePoint MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SharePoint MCP Server MCP server in PolicyLayer and add a rule for check_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 SharePoint MCP Server. Nothing to install.
check_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 check_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 check_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.
check_auth_status is provided by the SharePoint MCP Server MCP server (peacockery-studio/sharepoint-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 →