# get-glossary-info

Get metadata about a specific glossary

Agent View of the PolicyLayer registry record for `get-glossary-info`. HTML page: https://policylayer.com/tools/deepl/get-glossary-info

## Facts

- Tool: `get-glossary-info`
- Server: DeepL (`@deepl-mcp-server`) — https://policylayer.com/tools/deepl.md
- Install: `npx -y @deepl-mcp-server`
- Homepage: https://www.npmjs.com/package/@deepl-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade C, identity verified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-glossary-info",
    "arguments": {}
  }
}
```

## Why get-glossary-info is rated Low

This tool queries and retrieves metadata about an existing glossary. It performs a read-only operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could only discover glossary metadata, not alter data or trigger external actions.

From the tool's own definition: "Tool name 'get-glossary-info' and description 'Get metadata about a specific glossary' indicate a retrieval operation that returns information without modification or side effects."

## Use case

AI agents call get-glossary-info to retrieve information from DeepL 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 DeepL:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-glossary-info": {}
  }
}
```

## Other tools on DeepL (8)

- `translate-document` — Execute — https://policylayer.com/tools/deepl/translate-document.md
- `get-glossary-dictionary-entries` — Read — https://policylayer.com/tools/deepl/get-glossary-dictionary-entries.md
- `get-source-languages` — Read — https://policylayer.com/tools/deepl/get-source-languages.md
- `get-target-languages` — Read — https://policylayer.com/tools/deepl/get-target-languages.md
- `get-writing-styles` — Read — https://policylayer.com/tools/deepl/get-writing-styles.md
- `list-glossaries` — Read — https://policylayer.com/tools/deepl/list-glossaries.md
- `translate-text` — Read — https://policylayer.com/tools/deepl/translate-text.md
- `rephrase-text` — Write — https://policylayer.com/tools/deepl/rephrase-text.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=deepl · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deepl