AI agents call bungie_search_entities to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
entityType | string | Yes | |
searchTerm | string | Yes |
Parameters from the server's own tool schema.
This tool queries a game manifest database (Destiny 2) to retrieve entity information. It performs read-only data retrieval with no side effects, no code execution, no data modification, and no financial implications. The low severity reflects minimal blast radius if misused by an AI agent — worst case would be excessive queries or information disclosure about game data.
From the tool's definition Tool name contains 'search' and description states 'Search Destiny 2 manifest entities' — a retrieval operation with no modification capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Search Destiny 2 manifest entities. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bungie_search_entities accepts 3 parameters: api_key, entityType, searchTerm. Required: entityType, searchTerm. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for bungie_search_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 UnClick. Nothing to install.
bungie_search_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 bungie_search_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 bungie_search_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.
bungie_search_entities is provided by the UnClick MCP server (@unclick/mcp-server). 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 →