Clear all cached Ambient Weather data, forcing fresh data on the next request.
AI agents call reset_cache to permanently remove resources in Ambient — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly clears/deletes cached data. However, the blast radius is very low since the cache is just a performance optimization layer — no source data is lost, and the cache will be repopulated on the next request. It is classified as Destructive because the cache deletion itself cannot be undone (you can't restore the old cached state), but severity is low given the trivial real-world impact.
From the tool's definition Clear all cached Ambient Weather data, forcing fresh data on the next request.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all cached Ambient Weather data, forcing fresh data on the next request. It is categorised as a Destructive tool in the Ambient MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ambient MCP server in PolicyLayer and add a rule for reset_cache: 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 Ambient. Nothing to install.
reset_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_cache 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 reset_cache. 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.
reset_cache is provided by the Ambient MCP server (jrolstad/ambient-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 →