auth_status

Debug whether the Sanka CRM connector is authenticated. Do not use this as a preflight before company or contact lookup tools.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/auth-status.md

WHAT IT DOES

What auth_status does on Sanka MCP Server

AI agents call auth_status to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why auth_status is rated Low

This tool retrieves authentication status information only. It has no capability to modify data, execute commands, delete records, or commit financial transactions. The description explicitly notes it is for debugging purposes and should not be used as a preflight check, which further confirms its read-only nature.

From the tool's definition Tool name 'auth_status' and description 'Debug whether the Sanka CRM connector is authenticated' indicates it queries authentication state without modifying data or triggering side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auth_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For auth_status, this is the rule to start with:

auth_status Allowed

auth_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auth_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every auth_status call is checked against it from then on.

FAQ

Questions about auth_status

What does the auth_status tool do? +

Debug whether the Sanka CRM connector is authenticated. Do not use this as a preflight before company or contact lookup tools. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on auth_status? +

Register the Sanka 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 Sanka MCP Server. Nothing to install.

What risk level is auth_status? +

auth_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit auth_status? +

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.

How do I block auth_status completely? +

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.

What MCP server provides auth_status? +

auth_status is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →