Check if authentication credentials are available.
AI agents call auth_status to retrieve information from Onboarded MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—it retrieves information about authentication status without side effects. It does not create, modify, delete, or execute any operations. The minimal information leak of knowing whether credentials exist (versus their actual content) presents only low risk even if misused by an unauthorized agent.
From the tool's definition Tool name is 'auth_status' and description states it 'Check[s] if authentication credentials are available.' This is a simple status check that queries the state of authentication without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check if authentication credentials are available. It is categorised as a Read tool in the Onboarded MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Onboarded MCP Server 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 Onboarded MCP Server. 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 Onboarded MCP Server MCP server (onboardedinc/onboarded-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 →