AI agents use create_list_item to create or update resources in Slack Lists MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack Lists MCP Server environment.
This tool creates new list items in Slack, which is a reversible write operation. It modifies state by adding data but does not delete, execute arbitrary code, or move money. Severity is medium because creating unintended list items could clutter lists and impact team workflows, but the action is reversible.
From the tool's definition Tool name 'create_list_item' combined with server description stating it 'enables AI assistants to interact with Slack Lists through comprehensive tools for creating, retrieving, filtering, and managing list items.' The tool creates data in Slack Lists.
Documented attack patterns abuse exactly the kind of access create_list_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Slack Lists MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_list_item:
{
"version": "1",
"default": "deny",
"tools": {
"create_list_item": {
"limits": [
{
"counter": "create_list_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_list_item 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.
Free to start. No card required.
create_list_item. It is categorised as a Write tool in the Slack Lists MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack Lists MCP Server MCP server in PolicyLayer and add a rule for create_list_item: 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 Lists MCP Server. Nothing to install.
create_list_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_list_item 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 create_list_item. 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.
create_list_item is provided by the Slack Lists MCP Server MCP server (maplehilllabs/mcp-slack-lists). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Slack Lists MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Slack Lists MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.