New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

enterprise_search_get_connectors

List the workspace's enterprise search connectors.

SERVERSlack SOURCEkarbassi/slack-mcp
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/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'.

Questions about enterprise_search_get_connectors

What does the enterprise_search_get_connectors tool do? +

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.

How do I enforce a policy on enterprise_search_get_connectors? +

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.

What risk level is enterprise_search_get_connectors? +

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

Can I rate-limit enterprise_search_get_connectors? +

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.

How do I block enterprise_search_get_connectors completely? +

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.

What MCP server provides enterprise_search_get_connectors? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Slack's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.