AI agents call auth_status to retrieve information from Outpost without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple status check that returns information about the current authentication state. It has no side effects, does not create, modify, or delete data, and does not execute code or commit financial obligations. It is a straightforward read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'auth_status' and description 'Check if the user is authenticated with Microsoft' indicate a read-only query operation that retrieves authentication status without modifying any data or triggering external actions.
Attacks that exploit this kind of access
Check if the user is authenticated with Microsoft. It is categorised as a Read tool in the Outpost MCP Server, which means it retrieves data without modifying state.
Register the Outpost MCP server in PolicyLayer and add a rule for 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 Outpost. Nothing to install.
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 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 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.
auth_status is provided by the Outpost MCP server (signalclaude/outpost). 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 →