Get all unique tags across all documents in the RAG system.
AI agents call get_tags to retrieve information from RAG Document Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata (tags) from the RAG system without creating, modifying, or deleting any data. It has no ability to execute code, move money, or cause irreversible changes. The blast radius of misuse is minimal—an AI agent could only learn what tags exist in the system, which is non-sensitive organizational metadata. Classification as Read is appropriate.
From the tool's definition Tool name 'get_tags' and description 'Get all unique tags across all documents' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of retrieving metadata (tags) confirm this is a query operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get all unique tags across all documents in the RAG system. It is categorised as a Read tool in the RAG Document Server MCP Server, which means it retrieves data without modifying state.
Register the RAG Document Server MCP server in PolicyLayer and add a rule for get_tags: 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 RAG Document Server. Nothing to install.
get_tags 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_tags 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_tags. 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_tags is provided by the RAG Document Server MCP server (jaimeferj/mcp-rag-docs). 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 →