search_modules_dms

A read tool on the Slack MCP server.

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/search-modules-dms.md

WHAT IT DOES

What search_modules_dms does on Slack

AI agents call search_modules_dms 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.

RISK

Why search_modules_dms is rated Low

The tool appears to search or query direct messages in Slack, which is a read operation with no side effects. However, severity is high rather than low because searching DMs could expose sensitive personal communications if an AI agent misuses it with broad queries. The empty description reduces confidence, but the naming convention and server context justify the Read category classification.

From the tool's definition Tool name 'search_modules_dms' suggests searching direct messages; the broader server description mentions 'search' as a read capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_modules_dms 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_dms, this is the rule to start with:

search_modules_dms Allowed

search_modules_dms is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_modules_dms": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every search_modules_dms call is checked against it from then on.

FAQ

Questions about search_modules_dms

What does the search_modules_dms tool do? +

search_modules_dms 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.

How do I enforce a policy on search_modules_dms? +

Register the Slack MCP server in PolicyLayer and add a rule for search_modules_dms: 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 search_modules_dms? +

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

Can I rate-limit search_modules_dms? +

Yes. Add a rate_limit block to the search_modules_dms 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 search_modules_dms completely? +

Set action: deny in the PolicyLayer policy for search_modules_dms. 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 search_modules_dms? +

search_modules_dms 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.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →