ffbb_last_result
AI agents call ffbb_last_result 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 tool retrieves historical basketball match results from the French Basketball Federation. It performs a query operation with no side effects—it does not create, modify, delete, or execute any actions. The absence of a description lowers confidence slightly, but the naming convention and server context strongly suggest read-only access to past game data.
From the tool's definition Tool name 'ffbb_last_result' indicates retrieval of past match results. No description provided, but context from sibling tools (ffbb_lives, ffbb_next_match, ffbb_team_summary) all performing read-only operations on FFBB sports data, and the server's stated…
Attacks that exploit this kind of access
ffbb_last_result. 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_last_result: 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_last_result 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_last_result 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_last_result. 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_last_result 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 →