Debug whether the Sanka CRM connector is authenticated. Do not use this as a preflight before company or contact lookup tools.
AI agents call auth_status to retrieve information from Sanka 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 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
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.
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.
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 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.
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 →