検索インデックスを作成・更新します
AI agents use create_search_index to create or update resources in Claude MCP Server Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude MCP Server Integration environment.
This tool creates or modifies search index data, which is a Write category operation. It does not permanently delete data, execute arbitrary code, or move money. Severity is medium because misconfiguration could create a large index consuming resources or index sensitive file metadata, but the operation is reversible via re-indexing or deletion.
From the tool's definition Tool description in Japanese states '検索インデックスを作成・更新します' (creates/updates search index). The verbs 'create' (作成) and 'update' (更新) indicate reversible data modification.
Attacks that exploit this kind of access
検索インデックスを作成・更新します. It is categorised as a Write tool in the Claude MCP Server Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for create_search_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 Claude MCP Server Integration. Nothing to install.
create_search_index 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_search_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.
Set action: deny in the PolicyLayer policy for create_search_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.
create_search_index is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). 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 →