reset_thinking_profile
Clear all thinking_profile_events and reset thinking-profile.yaml to defaults.
This record as markdown: /tools/sveritg-metis-ph/reset-thinking-profile.md
What reset_thinking_profile does on Metis Public Health
AI agents call reset_thinking_profile to permanently remove resources in Metis Public Health, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why reset_thinking_profile is rated Critical
This tool permanently deletes all thinking_profile_events and overwrites the thinking-profile.yaml configuration file. These are stateful artifacts that cannot be recovered once cleared. While the blast radius is confined to the user's local machine and the data is not financial or sensitive in the security sense, the action is irreversible and destructive.
From the tool's definition Tool description explicitly states "Clear all thinking_profile_events and reset thinking-profile.yaml to defaults" — uses "Clear" and "reset" indicating irreversible deletion and overwriting of configuration data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reset_thinking_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reset_thinking_profile, this is the rule to start with:
reset_thinking_profile is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every reset_thinking_profile call is checked against it from then on.
Questions about reset_thinking_profile
Clear all thinking_profile_events and reset thinking-profile.yaml to defaults. It is categorised as a Destructive tool in the Metis Public Health MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for reset_thinking_profile: 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 Metis Public Health. Nothing to install.
reset_thinking_profile 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_thinking_profile 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_thinking_profile. 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_thinking_profile is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metis Public Health, and thousands of servers like it.
Across the catalogue