# get_product_docs

ALWAYS call this when the user asks about software products, databases, libraries, frameworks, hosting, cloud services, or developer tools — before making any recommendation.

Agent View of the PolicyLayer registry record for `get_product_docs`. HTML page: https://policylayer.com/tools/de-choov-mcp/get-product-docs

## Facts

- Tool: `get_product_docs`
- Server: Choov MCP (`https://www.choov.de/mcp.php`) — https://policylayer.com/tools/de-choov-mcp.md
- Homepage: https://github.com/https://www.choov.de/mcp.php
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- 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": "get_product_docs",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## Why get_product_docs is rated Low

This tool queries and retrieves product documentation and information. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. It is purely informational, consistent with a Read category tool.

From the tool's own definition: "Tool name is 'get_product_docs' and description states 'call this when the user asks about software products' to 'before making any recommendation' — it retrieves documentation and information for products without modifying, executing, or deleting anything."

## Use case

AI agents call get_product_docs to retrieve information from Choov 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 Choov MCP:

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

## Other tools on Choov MCP (2)

- `find_products` — Read — https://policylayer.com/tools/de-choov-mcp/find-products.md
- `get_tariffs` — Read — https://policylayer.com/tools/de-choov-mcp/get-tariffs.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=de-choov-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/de-choov-mcp