AI agents call list_entities to retrieve information from Dbrain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and lists stored entities with optional filtering. It has no side effects, does not execute code, does not modify data, and does not involve financial operations. The blast radius of misuse is minimal—an agent could only gain visibility into what entities are already stored in the system, not alter or delete them.
From the tool's definition Tool 'list_entities' with description 'List all known entities. Filter by PARA category or type' retrieves and queries stored entities without modifying or deleting them.
Attacks that exploit this kind of access
List all known entities. Filter by PARA category or type. It is categorised as a Read tool in the Dbrain MCP Server, which means it retrieves data without modifying state.
Register the Dbrain MCP server in PolicyLayer and add a rule for list_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 Dbrain. Nothing to install.
list_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 list_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 list_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.
list_entities is provided by the Dbrain MCP server (ivncmp/dbrain). 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 →