This record as markdown: /tools/karbassi-slack-mcp/search-modules-people.md
What search_modules_people does on Slack
AI agents call search_modules_people 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 search_modules_people is rated Low
The tool performs a search/query operation to retrieve information about people in Slack, which is a read-only action with no side effects. However, severity is elevated to medium because searching for people data could expose personally identifiable information (PII) or organizational structure details if misused by an agent, depending on access controls and what data is returned.
From the tool's definition Tool name 'search_modules_people' indicates a search operation querying people data. Server description states it provides 'search' capabilities for accessing Slack data. No modifying, destructive, or financial operations are implied.
Attacks that exploit this kind of access
The rule that runs search_modules_people 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 search_modules_people, this is the rule to start with:
search_modules_people 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 search_modules_people call is checked against it from then on.
Questions about search_modules_people
search_modules_people is a read tool on the Slack MCP server. 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 search_modules_people: 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.
search_modules_people 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 search_modules_people 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 search_modules_people. 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.
search_modules_people 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