保存済み検索を作成します
AI agents use create_saved_search 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 a new saved search object, which is a reversible write operation. It modifies state by adding a new record but does not execute queries, delete data, or access sensitive resources destructively. The low severity reflects that saved searches are typically benign configuration artifacts with minimal blast radius if misused.
From the tool's definition Tool name 'create_saved_search' and description '保存済み検索を作成します' (creates a saved search) indicate a create operation that generates or stores a new search configuration/entry.
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_saved_search: 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_saved_search 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_saved_search 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_saved_search. 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_saved_search 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 →