Shows a timeline of recent development activity in a project directory. Combines git commits, file modifications, and shell commands into a chronological view. Useful for understanding what happened in a project over a time period, or for reviewing your own recent work.
AI agents call recent_activity to retrieve information from Rewind without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
recent_activity is purely informational: it analyzes and presents git state, file activity history, and shell history in chronological order. There are no side effects, no code execution, no data modification, and no destructive operations. The worst-case misuse would be information disclosure of development history, which has low blast radius compared to other categories.
From the tool's definition Tool 'Shows a timeline of recent development activity' and 'reviewing your own recent work' — it retrieves and queries historical data (git commits, file modifications, shell commands) without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Shows a timeline of recent development activity in a project directory. Combines git commits, file modifications, and shell commands into a chronological view. Useful for understanding what happened in a project over a time period, or for reviewing your own recent work. It is categorised as a Read tool in the Rewind MCP Server, which means it retrieves data without modifying state.
Register the Rewind MCP server in PolicyLayer and add a rule for recent_activity: 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 Rewind. Nothing to install.
recent_activity 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 recent_activity 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 recent_activity. 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.
recent_activity is provided by the Rewind MCP server (vinitshahdeo/rewind-mcp). 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 →