This record as markdown: /tools/sveritg-metis-ph/get-glossary.md
What get_glossary does on Metis Public Health
AI agents call get_glossary to retrieve information from Metis Public Health without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_glossary is rated Low
This tool retrieves/queries existing glossary data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on the user's local glossary index. Low severity because glossary terms are typically non-sensitive reference data, and the blast radius of an AI agent retrieving this information is minimal.
From the tool's definition Tool name 'get_glossary' and description 'Retrieve all glossary terms' indicate a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_glossary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_glossary, this is the rule to start with:
get_glossary 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 Metis Public Health, apply this rule, and every get_glossary call is checked against it from then on.
Questions about get_glossary
Retrieve all glossary terms. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for get_glossary: 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 Metis Public Health. Nothing to install.
get_glossary 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 get_glossary 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 get_glossary. 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.
get_glossary is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metis Public Health, and thousands of servers like it.
This server
Across the catalogue