AI agents call get_list_items to retrieve information from Slack Lists MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries Slack List items without modifying, deleting, or executing operations. It aligns with the 'Read' category as it has no side effects. Severity is low because unauthorized retrieval of list data poses minimal immediate risk compared to destructive or financial operations, though sensitivity of the underlying data may vary by use case.
From the tool's definition Tool name 'get_list_items' combined with sibling tools including 'filter_list_items' and the server's stated capability for 'retrieving' list items indicates this is a data retrieval operation.
Documented attack patterns abuse exactly the kind of access get_list_items 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 get_list_items:
{
"version": "1",
"default": "deny",
"tools": {
"get_list_items": {}
}
}get_list_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_list_items. It is categorised as a Read tool in the Slack Lists MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Slack Lists MCP Server MCP server in PolicyLayer and add a rule for get_list_items: 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.
get_list_items 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 get_list_items 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 get_list_items. 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.
get_list_items 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.