enterprise_search_get_connectors
List the workspace's enterprise search connectors.
This record as markdown: /tools/karbassi-slack-mcp/enterprise-search-get-connectors.md
What enterprise_search_get_connectors does on Slack
AI agents call enterprise_search_get_connectors to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why enterprise_search_get_connectors is rated Low
This tool retrieves metadata about enterprise search connectors configured in the workspace. It performs no modifications, deletions, or external operations—purely a data query. The blast radius is minimal: an attacker gains visibility into connector configurations but cannot modify them or access sensitive data through this tool alone. Exposure is limited to informational disclosure about what connectors exist.
From the tool's definition Tool name 'enterprise_search_get_connectors' and description 'List the workspace's enterprise search connectors' indicate a retrieval operation with the verb 'List'.
Attacks that exploit this kind of access
The rule that runs enterprise_search_get_connectors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enterprise_search_get_connectors, this is the rule to start with:
enterprise_search_get_connectors is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every enterprise_search_get_connectors call is checked against it from then on.
Questions about enterprise_search_get_connectors
List the workspace's enterprise search connectors. 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 enterprise_search_get_connectors: 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.
enterprise_search_get_connectors 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 enterprise_search_get_connectors 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 enterprise_search_get_connectors. 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.
enterprise_search_get_connectors 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.
More on Slack, and thousands of servers like it.
This server
Across the catalogue