# get_pattern_details

A read tool on the 3ilm MCP server.

Agent View of the PolicyLayer registry record for `get_pattern_details`. HTML page: https://policylayer.com/tools/3ilm-mcp/get-pattern-details

## Facts

- Tool: `get_pattern_details`
- 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 |
| --- | --- | --- | --- |
| `pattern` | string | yes | Exact pattern name (kebab-case). One of: fee-miscalculation, dos-griefing, reentrancy, trusted-actor, overflow, staleness, rounding, access-control, oracle-mani |

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": "get_pattern_details",
    "arguments": {
      "pattern": "<pattern>"
    }
  }
}
```

## Why get_pattern_details is rated Low

The tool retrieves or queries data about patterns (presumably security patterns or vulnerability patterns) with no indication of side effects, modification, or execution capabilities. No description was provided, which slightly lowers confidence, but the naming convention and sibling tools strongly suggest informational/read-only functionality.

From the tool's own definition: "Tool name is 'get_pattern_details' and sibling tools are 'list_patterns' and 'search_vulnerabilities', indicating this server is a vulnerability/security pattern information system."

## Use case

AI agents call get_pattern_details 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": {
    "get_pattern_details": {}
  }
}
```

## Other tools on 3ilm (2)

- `list_patterns` — Read — https://policylayer.com/tools/3ilm-mcp/list-patterns.md
- `search_vulnerabilities` — Read — https://policylayer.com/tools/3ilm-mcp/search-vulnerabilities.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