List tournaments the logged-in user has joined.
AI agents call list_my_tournaments to retrieve information from Tulidu Sport without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about tournaments a user has joined. It performs a read-only query against user data without creating, modifying, deleting, executing external operations, or committing financial obligations. The blast radius of misuse is minimal—an unauthorized listing of a user's tournament memberships poses only a confidentiality risk, not integrity or availability risk.
From the tool's definition Tool description states 'List tournaments' which is a query/retrieval operation with no modification or side effects. The name 'list_my_tournaments' and description indicate data fetching only.
Attacks that exploit this kind of access
List tournaments the logged-in user has joined. It is categorised as a Read tool in the Tulidu Sport MCP Server, which means it retrieves data without modifying state.
Register the Tulidu Sport MCP server in PolicyLayer and add a rule for list_my_tournaments: 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 Tulidu Sport. Nothing to install.
list_my_tournaments 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 list_my_tournaments 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 list_my_tournaments. 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.
list_my_tournaments is provided by the Tulidu Sport MCP server (tulidu-sport/tulidu-sport-mcp). 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 →