lookup_entity
AI agents call lookup_entity to retrieve information from Chronicle SecOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or query entity information from Chronicle's security system without modifying data or triggering external operations. Lookup operations are characteristic of Read category tools. However, the empty description reduces confidence slightly; if it performs broader enrichment actions, classification could shift to Execute.
From the tool's definition Tool name 'lookup_entity' combined with sibling tools (get_ioc_matches, get_security_alerts, list_security_rules, search_security_events) and server description stating it 'looks up entities' within Chronicle Security Operations; empty tool description limits…
Attacks that exploit this kind of access
lookup_entity. It is categorised as a Read tool in the Chronicle SecOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chronicle SecOps MCP Server 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 Chronicle SecOps MCP Server. Nothing to install.
lookup_entity 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 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.
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.
lookup_entity is provided by the Chronicle SecOps MCP Server MCP server (mcpflow/mcp-secops-v3). 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 →