Low Risk

search_vault

Search the user's knowledge vault for notes matching a query. Returns titles, IDs, tags, and content snippets.

Risk signalsAccepts freeform code/query input (query)

Part of the Dyer Md server.

search_vault is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DYER MD →

Free to start. No card required.

AI agents call search_vault to retrieve information from Dyer Md without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_vault only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_vault": {}
  }
}

See the full Dyer Md policy for all 12 tools.

Get this rule live on your own Dyer Md server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DYER MD →

View all 12 tools →

These attack patterns abuse exactly the kind of access search_vault gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so search_vault only ever does what you allow.

SECURE DYER MD →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_vault tool do? +

Search the user's knowledge vault for notes matching a query. Returns titles, IDs, tags, and content snippets.. It is categorised as a Read tool in the Dyer Md MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_vault? +

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

What risk level is search_vault? +

search_vault is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_vault? +

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

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

search_vault is provided by the Dyer Md MCP server (dyer-md-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dyer Md tool call.

Deterministic rules across all 12 Dyer Md tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.