Get frequency count for all canonical tags.
AI agents call get_tag_frequencies to retrieve information from Vector Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information about tag usage frequencies from the vector memory database. It performs a read-only query operation with no side effects, no data modification, no code execution, and no destructive capabilities. The lowest blast radius would result from misuse—an AI agent could only retrieve tag frequency data, which poses minimal security risk.
From the tool's definition Tool name 'get_tag_frequencies' and description 'Get frequency count for all canonical tags' indicate a retrieval operation that queries aggregated tag statistics without modifying any data.
Attacks that exploit this kind of access
Get frequency count for all canonical tags. It is categorised as a Read tool in the Vector Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Vector Memory MCP server in PolicyLayer and add a rule for get_tag_frequencies: 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 Vector Memory MCP. Nothing to install.
get_tag_frequencies 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_tag_frequencies 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_tag_frequencies. 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_tag_frequencies is provided by the Vector Memory MCP server (xsaven/vector-memory-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 →