List all available authentication methods
AI agents call list_auth_methods 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 configuration data about available authentication methods in PocketBase. It performs no mutations, executions, or destructive operations. The information exposed (available auth methods) is typically non-sensitive configuration metadata. Misuse would have minimal blast radius—an AI agent could only learn what auth methods are available, not authenticate users or modify the system.
From the tool's definition Tool name 'list_auth_methods' and description 'List all available authentication methods' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_auth_methods 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 list_auth_methods:
{
"version": "1",
"default": "deny",
"tools": {
"list_auth_methods": {}
}
}list_auth_methods 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.
List all available authentication methods. 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 list_auth_methods: 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.
list_auth_methods 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 list_auth_methods 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 list_auth_methods. 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.
list_auth_methods is provided by the PocketBase MCP Server MCP server (mrwyndham/pocketbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PocketBase 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.
24 PocketBase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.