# search_capabilities

Keyword search across FEODE products/specs. e.g. 'subsea wellhead 15000 psi', 'one trip abandonment', 'continuous circulation'.

Agent View of the PolicyLayer registry record for `search_capabilities`. HTML page: https://policylayer.com/tools/com-feode-feode-mcp/search-capabilities

## Facts

- Tool: `search_capabilities`
- Server: Feode Mcp (`https://www.feode.com/mcp`) — https://policylayer.com/tools/com-feode-feode-mcp.md
- Homepage: https://github.com/FarEastAI/feode-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `query` | string | yes |  |

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_capabilities",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## Why search_capabilities is rated Low

This tool performs information retrieval only. It searches and returns product specifications and capabilities without creating, modifying, executing, deleting, or committing financial resources. The examples ('subsea wellhead 15000 psi', 'one trip abandonment', 'continuous circulation') are search queries, not directives that trigger external actions or state changes.

From the tool's own definition: "Tool name 'search_capabilities' and description indicates 'Keyword search across FEODE products/specs' — a query-based retrieval operation with no side effects."

## Use case

AI agents call search_capabilities to retrieve information from Feode Mcp 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 Feode Mcp:

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

## Other tools on Feode Mcp (11)

- `get_certifications` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-certifications.md
- `get_company_profile` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-company-profile.md
- `get_drill_pipe_specs` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-drill-pipe-specs.md
- `get_drill_string_guidance` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-drill-string-guidance.md
- `get_machining_services` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-machining-services.md
- `get_machining_terms` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-machining-terms.md
- `get_product_specs` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-product-specs.md
- `list_drill_pipe` — Read — https://policylayer.com/tools/com-feode-feode-mcp/list-drill-pipe.md
- `list_products` — Read — https://policylayer.com/tools/com-feode-feode-mcp/list-products.md
- `search_drill_pipe` — Read — https://policylayer.com/tools/com-feode-feode-mcp/search-drill-pipe.md
- `submit_machining_rfq` — Write — https://policylayer.com/tools/com-feode-feode-mcp/submit-machining-rfq.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=com-feode-feode-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-feode-feode-mcp
