AI agents call list_entities to retrieve information from Tecton without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about entities from a Tecton cluster. It performs no modifications, deletions, or executions—it only retrieves information. The blast radius of misuse is minimal; an agent listing entities cannot damage systems or data, only access metadata that may already be queryable through other means.
From the tool's definition Tool name 'list_entities' and description 'List all entities in the currently connected tecton cluster' indicate a retrieval operation with no side effects. The verb 'list' is a canonical Read operation.
Attacks that exploit this kind of access
List all entities in the currently connected tecton cluster. It is categorised as a Read tool in the Tecton MCP Server, which means it retrieves data without modifying state.
Register the Tecton 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 Tecton. 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 Tecton MCP server (slavovthinks/tecton-mcp). 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 →