entity_present_details

A write tool on the Slack MCP server.

SERVERSlack SOURCEkarbassi/slack-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/entity-present-details.md

WHAT IT DOES

What entity_present_details does on Slack

AI agents use entity_present_details to create or update resources in Slack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.

RISK

Why entity_present_details is rated Medium

An AI agent can call entity_present_details faster than any human can review: one bad instruction and it creates or modifies resources in Slack by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

entity_present_details Rate-limited

entity_present_details stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "entity_present_details": {
      "limits": [
        {
          "counter": "entity_present_details_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about entity_present_details

What does the entity_present_details tool do? +

entity_present_details is a write tool on the Slack MCP server. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on entity_present_details? +

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

entity_present_details is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit entity_present_details? +

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

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

entity_present_details 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →