Most-mentioned entities of a given type (e.g. top env vars, top slash commands). Useful for
AI agents call top_entities to retrieve information from Claude Synergy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a local changelog database to retrieve statistical information about frequently-mentioned entities (environment variables, commands, etc.). It has no side effects, does not execute code, does not modify data, and does not create obligations. It is purely informational/analytical.
From the tool's definition Tool name 'top_entities' and description 'Most-mentioned entities of a given type' indicate a retrieval/query operation that scans a changelog mirror to identify and return aggregate statistics.
Attacks that exploit this kind of access
Most-mentioned entities of a given type (e.g. top env vars, top slash commands). Useful for. It is categorised as a Read tool in the Claude Synergy MCP Server, which means it retrieves data without modifying state.
Register the Claude Synergy MCP server in PolicyLayer and add a rule for top_entities: 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 Claude Synergy. Nothing to install.
top_entities 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 top_entities 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 top_entities. 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.
top_entities is provided by the Claude Synergy MCP server (mcp-tool-shop-org/claude-synergy). 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 →