create_test_index · Search MCP: Risk & Policy

WHAT IT DOES

What create_test_index does on Search MCP

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

WHY IT NEEDS A POLICY

Why create_test_index needs a policy

This tool creates new data structures (Elasticsearch test indices) with sample documents. Creation is reversible (the index can be deleted), making this a Write operation rather than Read or Destructive. Severity is low because test indices with sample data pose minimal risk—they are isolated from production systems and intended for demonstration.

From the tool's definition Tool name 'create_test_index' and description 'Create a test index with sample documents' indicate data creation. The qualifier 'test' and 'demonstration purposes' suggest this operates on ephemeral, non-production data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_test_index Rate-limited

create_test_index 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": {
    "create_test_index": {
      "limits": [
        {
          "counter": "create_test_index_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 Search MCP, so you can run agents against it safely.

FAQ

Questions about create_test_index

What does the create_test_index tool do? +

Create a test index with sample documents for demonstration purposes. It is categorised as a Write tool in the Search MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_test_index? +

Register the Search MCP server in PolicyLayer and add a rule for create_test_index: 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 Search MCP. Nothing to install.

What risk level is create_test_index? +

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

Can I rate-limit create_test_index? +

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

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

create_test_index is provided by the Search MCP server (piscaries/search_mcp_demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.