get_top_buckets_by_operations
AI agents call get_top_buckets_by_operations to retrieve information from Team MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve metrics or statistics about buckets ranked by operation count—a data query with no modification or side effects. Despite the empty description lowering confidence slightly, the naming convention and context strongly suggest a read-only retrieval operation. No evidence of write, execute, destructive, or financial capabilities.
From the tool's definition Tool name 'get_top_buckets_by_operations' indicates a retrieval/query operation. Description is empty, but the naming pattern and sibling tools (get_team_name, get_top_buckets_by_inbound_traffic, list_buckets) all indicate read-only data retrieval operations.
Attacks that exploit this kind of access
get_top_buckets_by_operations. It is categorised as a Read tool in the Team MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Team MCP Server MCP server in PolicyLayer and add a rule for get_top_buckets_by_operations: 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 Team MCP Server. Nothing to install.
get_top_buckets_by_operations 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 get_top_buckets_by_operations 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 get_top_buckets_by_operations. 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.
get_top_buckets_by_operations is provided by the Team MCP Server MCP server (mistral-mcp-hackathon/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 →