Get a summary of activity across all registered projects, sorted by momentum. Shows what the developer is working on across their entire portfolio.
AI agents call get_whats_hot to retrieve information from KeepGoing 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 and aggregates existing project activity data (momentum metrics and current work items) without creating, modifying, deleting, or executing any operations. It has no side effects and presents no financial or destructive risk. The blast radius is minimal—misuse would only expose development activity summaries that the user/agent already has access to within their own project portfolio.
From the tool's definition Tool name 'get_whats_hot' and description 'Get a summary of activity across all registered projects' indicate retrieval of existing data without modification. The term 'Get' and 'summary' confirm read-only behavior.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get a summary of activity across all registered projects, sorted by momentum. Shows what the developer is working on across their entire portfolio. It is categorised as a Read tool in the KeepGoing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KeepGoing MCP Server MCP server in PolicyLayer and add a rule for get_whats_hot: 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 KeepGoing MCP Server. Nothing to install.
get_whats_hot 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_whats_hot 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_whats_hot. 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_whats_hot is provided by the KeepGoing MCP Server MCP server (keepgoing-dev/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 →