ffbb_search
AI agents call ffbb_search 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.
This is a search tool operating on a read-only sports data API. No side effects, modifications, deletions, or financial transactions are possible. The tool retrieves basketball-related information matching the federation's public data access pattern. The empty description reduces confidence slightly, but the clear context from server purpose and sibling tools strongly indicates Read category.
From the tool's definition Tool name 'ffbb_search' and server context indicate data retrieval from French Basketball Federation. Sibling tools (ffbb_lives, ffbb_last_result, ffbb_next_match, ffbb_club, ffbb_get) are all read-only queries.
Attacks that exploit this kind of access
ffbb_search. 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_search: 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_search 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_search 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_search. 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_search 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.
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 →