List available domain glossary keys.
AI agents call list_glossary to retrieve information from Aurora-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple enumeration/listing of glossary keys, which is a read-only operation with no side effects. It retrieves information about what glossary terms are available in the system. There is no data modification, code execution, deletion, or financial impact. The blast radius of misuse is minimal—an agent could only learn what terms exist in the glossary, which is non-sensitive metadata retrieval.
From the tool's definition Tool name 'list_glossary' and description 'List available domain glossary keys' indicate a retrieval operation that returns metadata about available glossary terms without modifying any data.
Attacks that exploit this kind of access
List available domain glossary keys. It is categorised as a Read tool in the Aurora-MCP MCP Server, which means it retrieves data without modifying state.
Register the Aurora- MCP server in PolicyLayer and add a rule for list_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 Aurora-MCP. Nothing to install.
list_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 list_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 list_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.
list_glossary is provided by the Aurora- MCP server (ndaniel/aurora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →