lichess_get_team
Get information about a Lichess team: description, member count, leader, open/closed status.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/lichess-get-team.md
What lichess_get_team does on Sports Hub
AI agents call lichess_get_team to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why lichess_get_team is rated Low
This tool retrieves and queries publicly available team information from Lichess. It performs a GET operation that returns static data (description, member count, leader, status) without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only retrieve information that is already public on Lichess.
From the tool's definition Tool name 'lichess_get_team' and description 'Get information about a Lichess team: description, member count, leader, open/closed status' indicate retrieval of read-only team metadata with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs lichess_get_team safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lichess_get_team, this is the rule to start with:
lichess_get_team 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 Sports Hub, apply this rule, and every lichess_get_team call is checked against it from then on.
Questions about lichess_get_team
Get information about a Lichess team: description, member count, leader, open/closed status. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for lichess_get_team: 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 Sports Hub. Nothing to install.
lichess_get_team 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 lichess_get_team 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 lichess_get_team. 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.
lichess_get_team is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue