This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/nba-players.md
What nba_players does on UnClick
AI agents call nba_players 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 |
|---|---|---|---|
limit | number | — | Results per page (default 25) |
search | string | — | Player name to search for |
Parameters from the server's own tool schema.
Why nba_players is rated Low
This is a straightforward read-only lookup tool that searches a database of NBA players by name and returns results. No data is created, modified, deleted, or any external operations are triggered. The blast radius of misuse is minimal — an attacker could only retrieve publicly available NBA player information.
From the tool's definition Tool description states 'Search NBA players by name' — a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs nba_players 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 nba_players, this is the rule to start with:
nba_players 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 nba_players call is checked against it from then on.
Questions about nba_players
Search NBA players by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
nba_players accepts 2 parameters: limit, search. 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 nba_players: 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.
nba_players 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 nba_players 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 nba_players. 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.
nba_players 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue