# search_vulnerabilities

A read tool on the 3ilm MCP server.

Agent View of the PolicyLayer registry record for `search_vulnerabilities`. HTML page: https://policylayer.com/tools/3ilm-mcp/search-vulnerabilities

## Facts

- Tool: `search_vulnerabilities`
- Server: 3ilm (`3ilm-mcp`) — https://policylayer.com/tools/3ilm-mcp.md
- Install: `npx -y 3ilm-mcp`
- Homepage: https://github.com/holistis/3ilm-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `query` | string | yes | Keyword search query. Examples: "oracle price manipulation", "reentrancy", "fee calculation", "flash loan", "access control", "rounding error" |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_vulnerabilities",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## Why search_vulnerabilities is rated Low

Search operations retrieve and query data without modifying state or triggering external actions. The lack of language suggesting creation, deletion, execution, or financial impact places this firmly in the Read category. Severity is low because unauthorized vulnerability data queries, while undesirable, do not directly cause damage compared to destructive or executable tools.

From the tool's own definition: "Tool name 'search_vulnerabilities' indicates a query/search operation. The verb 'search' is typical of retrieval operations with no side effects."

## Use case

AI agents call search_vulnerabilities to retrieve information from 3ilm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 3ilm:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_vulnerabilities": {}
  }
}
```

## Other tools on 3ilm (2)

- `get_pattern_details` — Read — https://policylayer.com/tools/3ilm-mcp/get-pattern-details.md
- `list_patterns` — Read — https://policylayer.com/tools/3ilm-mcp/list-patterns.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=3ilm-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/3ilm-mcp