Low Risk

list_entities

Returns a paginated list of corporate entities in the TunnelMind surveillance database. Includes data categories, estimated data value, and industry classification. Useful for enumerating the surveillance ecosystem by sector. Use this tool when: - You want to enumerate all entities in a specific ...

Part of the TunnelMind Data API server.

list_entities is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TUNNELMIND DATA API →

Free to start. No card required.

AI agents call list_entities to retrieve information from TunnelMind Data API without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_entities only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_entities": {}
  }
}

See the full TunnelMind Data API policy for all 54 tools.

Get this rule live on your own TunnelMind Data API server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TUNNELMIND DATA API →

View all 54 tools →

These attack patterns abuse exactly the kind of access list_entities gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_entities only ever does what you allow.

SECURE TUNNELMIND DATA API →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_entities tool do? +

Returns a paginated list of corporate entities in the TunnelMind surveillance database. Includes data categories, estimated data value, and industry classification. Useful for enumerating the surveillance ecosystem by sector. Use this tool when: - You want to enumerate all entities in a specific industry (e.g., all ad-tech companies). - You need a dataset of surveillance entities for analysis or reporting. - You are building a comprehensive surveillance landscape map. Do NOT use this tool when: - You need the full profile of a specific entity — use get_entity instead. - You are searching by entity name — use search instead. - You need domain-level data — use list_domains instead. Inputs: - industry (query, optional): Filter by industry classification. Examples: ad_tech, analytics, data_broker, social, crm. - limit (query, optional): Results per page. Max 100 (paid), 20 (free). Default 50. - cursor (query, optional): Pagination cursor from previous response's next_cursor. Returns: - Array of entity list items (slug, name, parent_company, industry, data_categories, data_cost_usd). - meta.has_more and meta.next_cursor for pagination. Cost: - Free tier: up to 20 results/page, 50 req/day. Pro/enterprise: up to 100 results/page. Latency: - Typical: <150ms, p99: <400ms.. It is categorised as a Read tool in the TunnelMind Data API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_entities? +

Register the TunnelMind Data API 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 TunnelMind Data API. Nothing to install.

What risk level is list_entities? +

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

Can I rate-limit list_entities? +

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.

How do I block list_entities completely? +

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.

What MCP server provides list_entities? +

list_entities is provided by the TunnelMind Data API MCP server (https://mcp-data.tunnelmind.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TunnelMind Data API tool call.

Deterministic rules across all 54 TunnelMind Data API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.