ffbb_lives
AI agents call ffbb_lives to retrieve information from FFBB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server's stated purpose of providing read-only access to French Basketball Federation data (scores, standings, competition details) and the pattern of sibling tools that are clearly retrieval-oriented (search, get, summary, bilan), ffbb_lives almost certainly retrieves live score data without side effects. No credentials required, no data modification capability mentioned.
From the tool's definition Tool name 'ffbb_lives' with sibling tools like 'ffbb_last_result', 'ffbb_next_match', and 'ffbb_get' indicates data retrieval.
Attacks that exploit this kind of access
ffbb_lives. It is categorised as a Read tool in the FFBB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FFBB MCP Server MCP server in PolicyLayer and add a rule for ffbb_lives: 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 FFBB MCP Server. Nothing to install.
ffbb_lives 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 ffbb_lives 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 ffbb_lives. 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.
ffbb_lives is provided by the FFBB MCP Server MCP server (nickdesi/ffbb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ffbb_lives is one line of FFBB MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →