slack_auth_test

Check authentication and get workspace/user information

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/slack-auth-test.md

WHAT IT DOES

What slack_auth_test does on Sage MCP

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

RISK

Why slack_auth_test is rated Low

This tool performs authentication validation and information retrieval only. It queries Slack for workspace and user details (a GET/READ operation) with no side effects, data modification, code execution, or destructive capability. The low severity reflects minimal blast radius—misuse would only expose already-authenticated user information to the AI agent, not alter Slack data or trigger external actions.

From the tool's definition Tool name 'slack_auth_test' and description 'Check authentication and get workspace/user information' indicate a read-only operation that retrieves user and workspace metadata without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slack_auth_test safely

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

slack_auth_test Allowed

slack_auth_test 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": {
    "slack_auth_test": {}
  }
}

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

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

FAQ

Questions about slack_auth_test

What does the slack_auth_test tool do? +

Check authentication and get workspace/user information. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on slack_auth_test? +

Register the Sage MCP server in PolicyLayer and add a rule for slack_auth_test: 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 Sage MCP. Nothing to install.

What risk level is slack_auth_test? +

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

Can I rate-limit slack_auth_test? +

Yes. Add a rate_limit block to the slack_auth_test 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 slack_auth_test completely? +

Set action: deny in the PolicyLayer policy for slack_auth_test. 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 slack_auth_test? +

slack_auth_test is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

The MCP Attack Database →

Guides

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