This record as markdown: /tools/creativelead-unclick/bungie-get-profile.md
What bungie_get_profile does on UnClick
AI agents call bungie_get_profile 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 | — | |
membershipId | string | — | |
membershipType | number | — |
Parameters from the server's own tool schema.
Why bungie_get_profile is rated Low
This tool retrieves player profile information from Destiny 2 (Bungie API). It performs a read-only query operation that returns public or authorized player data without modifying, executing code, deleting data, or affecting financial transactions. The action is informational only, making it a Read category tool with low severity since profile data exposure is generally limited in scope and impact.
From the tool's definition Tool name 'get_profile' and description 'Get a Destiny 2 player profile' indicate data retrieval with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs bungie_get_profile 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_get_profile, this is the rule to start with:
bungie_get_profile 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_get_profile call is checked against it from then on.
Questions about bungie_get_profile
Get a Destiny 2 player profile. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bungie_get_profile accepts 3 parameters: api_key, membershipId, membershipType. 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_get_profile: 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_get_profile 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_get_profile 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_get_profile. 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_get_profile 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