lookup_entity

Find every release that mentions a specific entity: env var, slash command, CLI option, model ID, beta header, hook event, CVE, GHSA. Returns chronological history of mentions across products.

Server Claude Synergy mcp-tool-shop-org/claude-synergy
Category Read
Risk class Low
Parameters 00 required

What lookup_entity does on Claude Synergy

AI agents call lookup_entity 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.

Why lookup_entity needs a policy

This is a search/lookup operation over a changelog database. It queries and retrieves information about entities (env vars, CLI options, model IDs, CVEs, etc.) mentioned in release notes. No modifications, executions, or destructive operations are possible. The blast radius of misuse is minimal—an agent might retrieve irrelevant changelog entries, but cannot cause harm through this tool alone.

From the tool's definition Tool 'returns chronological history of mentions' and 'find every release that mentions' — purely retrieves/queries existing changelog data without creating, modifying, executing operations, or deleting anything. No side effects.

Questions about lookup_entity

What does the lookup_entity tool do? +

Find every release that mentions a specific entity: env var, slash command, CLI option, model ID, beta header, hook event, CVE, GHSA. Returns chronological history of mentions across products. It is categorised as a Read tool in the Claude Synergy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_entity? +

Register the Claude Synergy MCP server in PolicyLayer and add a rule for lookup_entity: 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.

What risk level is lookup_entity? +

lookup_entity is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lookup_entity? +

Yes. Add a rate_limit block to the lookup_entity 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.

How do I block lookup_entity completely? +

Set action: deny in the PolicyLayer policy for lookup_entity. 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.

What MCP server provides lookup_entity? +

lookup_entity 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.