AI agents call bungie_search_player 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 | — | |
displayName | string | Yes | |
membershipType | number | — | -1 for all |
Parameters from the server's own tool schema.
This tool performs a search/lookup operation on public player data in the Destiny 2 game. It retrieves information based on a display name query, which is a read-only operation with no side effects, data modification, code execution, or financial implications. The blast radius of misuse is minimal—an agent could only retrieve publicly available player information.
From the tool's definition Tool name 'bungie_search_player' and description 'Search for a Destiny 2 player by display name' indicate a query operation that retrieves player information without modifying, deleting, or executing code.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Search for a Destiny 2 player by display name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bungie_search_player accepts 3 parameters: api_key, displayName, membershipType. Required: displayName. 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_player: 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_player 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_player 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_player. 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_player 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 →