Check current authentication status and get current user info.
AI agents call get_auth_status to retrieve information from PocketBase 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 metadata and user information. It performs no data mutations, does not execute code or commands, and has no destructive or financial impact. The blast radius of misuse is minimal—an agent could only learn about the current auth state, which is typically already known to the authenticated session. This is a classic Read operation.
From the tool's definition Tool name 'get_auth_status' and description 'Check current authentication status and get current user info' indicate a query operation that retrieves information without modifying data or triggering 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 PocketBase 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 current authentication status and get current user info. It is categorised as a Read tool in the PocketBase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PocketBase 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 PocketBase 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 PocketBase MCP Server MCP server (ssakone/pb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 PocketBase MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 PocketBase MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.