AI agents call get_context_status 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.
This tool reads and queries internal state of the Rewind agent (status, metadata, counts, storage information). It has no side effects, does not modify data, execute operations, or access sensitive external systems. The most severe risk is potential information disclosure about what the agent is tracking, which is low impact in most contexts.
From the tool's definition Tool name and description indicate it 'Shows the current status' and provides information about 'tracked directories, snapshot counts, and storage info' — purely informational retrieval with no modification or execution.
Attacks that exploit this kind of access
Shows the current status of the Rewind agent: tracked directories, snapshot counts, and storage info. Useful for understanding what the agent knows about and managing its state. 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 get_context_status: 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.
get_context_status 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_context_status 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_context_status. 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_context_status 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 →