index_custom_content · Slite MCP Server MCP: Risk & Policy

WHAT IT DOES

What index_custom_content does on Slite MCP Server

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

WHY IT NEEDS A POLICY

Why index_custom_content needs a policy

Indexing content involves writing/pushing data into a search or AI index system (AskX). This is a write operation as it creates or modifies indexed data. The tool is marked deprecated, which lowers confidence slightly. Severity is medium as misuse could corrupt or pollute the knowledge base index, but it's reversible.

From the tool's definition Index custom content to AskX in Slite (deprecated)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

index_custom_content Rate-limited

index_custom_content 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": {
    "index_custom_content": {
      "limits": [
        {
          "counter": "index_custom_content_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Slite MCP Server, so you can run agents against it safely.

FAQ

Questions about index_custom_content

What does the index_custom_content tool do? +

Index custom content to AskX in Slite (deprecated). It is categorised as a Write tool in the Slite MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on index_custom_content? +

Register the Slite MCP Server MCP server in PolicyLayer and add a rule for index_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.

What risk level is index_custom_content? +

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

Can I rate-limit index_custom_content? +

Yes. Add a rate_limit block to the index_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.

How do I block index_custom_content completely? +

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

What MCP server provides index_custom_content? +

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