save_search · Assetcache MCP: Risk & Policy

WHAT IT DOES

What save_search does on Assetcache

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

WHY IT NEEDS A POLICY

Why save_search needs a policy

The tool creates and stores a named search configuration, which is a Write operation—data is being created or modified reversibly. It does not retrieve assets (Read), execute arbitrary code (Execute), delete anything (Destructive), or involve money (Financial).

From the tool's definition Tool name 'save_search' and description indicate it saves/stores a named search query ("검색 요청을 이름 붙여 저장한다" = 'saves a named search request'). This is a reversible create/store operation on metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_search Rate-limited

save_search 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": {
    "save_search": {
      "limits": [
        {
          "counter": "save_search_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 Assetcache, so you can run agents against it safely.

FAQ

Questions about save_search

What does the save_search tool do? +

검색 요청을 이름 붙여 저장한다 (project_id 별 unique name). It is categorised as a Write tool in the Assetcache MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_search? +

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

What risk level is save_search? +

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

Can I rate-limit save_search? +

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

How do I block save_search completely? +

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

What MCP server provides save_search? +

save_search is provided by the Assetcache MCP server (v0o0v/assetcache-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.