This record as markdown: /tools/creativelead-unclick/bungie-search-entities.md
What bungie_search_entities does on UnClick
AI agents call bungie_search_entities to retrieve information from UnClick without modifying anything. It is 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 | — | |
searchTerm | string | — |
Parameters from the server's own tool schema.
Why bungie_search_entities is rated Low
This tool performs a read-only search operation against the Destiny 2 manifest. It retrieves and queries existing data with no side effects, no data modification, no code execution, and no destructive actions. Typical blast radius if misused by an AI agent would be low—worst case is information disclosure or rate-limiting from excessive queries.
From the tool's definition Tool name 'bungie_search_entities' with verb 'search' and description 'Search Destiny 2 manifest entities' indicates a query operation retrieving data from the Bungie/Destiny 2 service without modification.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs bungie_search_entities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bungie_search_entities, this is the rule to start with:
bungie_search_entities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every bungie_search_entities call is checked against it from then on.
Questions about bungie_search_entities
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. 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 (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue