This record as markdown: /tools/deepl/list-glossaries.md
What list-glossaries does on DeepL
AI agents call list-glossaries 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.
Why list-glossaries is rated Low
This tool retrieves and lists glossary information without side effects. It is a read-only operation that queries existing data. The low severity reflects that exposure of glossary metadata poses minimal risk compared to tools that could execute code, modify data, or trigger external operations.
From the tool's definition Tool is named 'list-glossaries' and described as 'List all glossaries and their metadata' — a pure query operation with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs list-glossaries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DeepL, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list-glossaries, this is the rule to start with:
list-glossaries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DeepL, apply this rule, and every list-glossaries call is checked against it from then on.
Questions about list-glossaries
List all glossaries and their metadata. It is categorised as a Read tool in the DeepL MCP Server, which means it retrieves data without modifying state.
Register the DeepL MCP server in PolicyLayer and add a rule for list-glossaries: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches DeepL. Nothing to install.
list-glossaries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-glossaries rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list-glossaries. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list-glossaries is provided by the DeepL MCP server (@deepl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DeepL, and thousands of servers like it.
This server
Across the catalogue