AI agents call session_test to retrieve information from Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a validation check on authentication tokens, which is a read operation that retrieves or queries token state without side effects. It does not create, modify, delete, or execute any operations—it merely verifies the validity of existing session credentials. The blast radius is minimal: misuse would only reveal whether a token is valid, not expose sensitive data or enable further actions directly.
From the tool's definition Tool name 'session_test' and description 'Check if session tokens (xoxc/xoxd) are valid' indicate a read-only validation operation that queries token status without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Check if session tokens (xoxc/xoxd) are valid. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for session_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 Slack. Nothing to install.
session_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 session_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 session_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.
session_test is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
session_test is one line of Slack's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →