get_entities
AI agents call get_entities to retrieve information from DataHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and sibling tools (list_schema_fields, search, get_lineage) suggest this is a data retrieval operation. Without an explicit description, we infer it is a read-only query operation consistent with the server's exploratory and informational focus. No destructive, financial, or code execution capabilities are evident. Confidence is reduced due to missing explicit description.
From the tool's definition Tool name 'get_entities' implies retrieval of entity information. No description provided, but based on the server's stated purpose of enabling agents to 'search, explore data lineage, understand business context,' this tool likely retrieves metadata or…
Attacks that exploit this kind of access
get_entities. It is categorised as a Read tool in the DataHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DataHub MCP Server MCP server in PolicyLayer and add a rule for get_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 DataHub MCP Server. Nothing to install.
get_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 get_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 get_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.
get_entities is provided by the DataHub MCP Server MCP server (shemreader/mcp-server-datahub). 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 →