AI agents call whats_new to retrieve information from Kontexta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and lists files that have changed since a given checkpoint. It performs no modifications, deletions, or executions — purely a read/query operation with minimal blast radius if misused.
From the tool's definition List files created or modified since a checkpoint
Attacks that exploit this kind of access
List files created or modified since a checkpoint. It is categorised as a Read tool in the Kontexta MCP Server, which means it retrieves data without modifying state.
Register the Kontexta MCP server in PolicyLayer and add a rule for whats_new: 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 Kontexta. Nothing to install.
whats_new 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 whats_new 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 whats_new. 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.
whats_new is provided by the Kontexta MCP server (safiyu/kontexta). 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 →