List indexed custom content IDs from AskX in Slite (deprecated)
AI agents call list_custom_content to retrieve information from Slite 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 lists custom content IDs without modifying, deleting, or executing code. It is a read-only operation with no side effects. The low severity reflects minimal blast radius—listing indexed content poses no direct harm if misused by an AI agent, particularly given its deprecated status.
From the tool's definition Tool name 'list_custom_content' and description 'List indexed custom content IDs' indicate a retrieval operation with no modification or deletion. The deprecated status suggests this is a passive query operation.
Attacks that exploit this kind of access
List indexed custom content IDs from AskX in Slite (deprecated). It is categorised as a Read tool in the Slite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Slite MCP Server MCP server in PolicyLayer and add a rule for list_custom_content: 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 Slite MCP Server. Nothing to install.
list_custom_content 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 list_custom_content 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 list_custom_content. 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.
list_custom_content is provided by the Slite MCP Server MCP server (takeokunn/slite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →