AI agents call slack_auth_test to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access slack_auth_test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for slack_auth_test:
{
"version": "1",
"default": "deny",
"tools": {
"slack_auth_test": {}
}
}slack_auth_test 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 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.
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.
slack_auth_test 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 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.
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.
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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.