Overwrite all constitutional rules for this session
AI agents call reset_constitution to permanently remove resources in Mcp Vibe Check — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly replaces the entire set of constitutional rules governing the session. Once overwritten, the previous rules are lost and cannot be recovered within that session context. This is a destructive operation even if technically reversible across session boundaries, because it eliminates the current operational guidelines.
From the tool's definition Tool description explicitly states "Overwrite all constitutional rules for this session" — 'overwrite' indicates irreversible replacement of existing data/configuration.
Attacks that exploit this kind of access
Overwrite all constitutional rules for this session. It is categorised as a Destructive tool in the Mcp Vibe Check MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Vibe Check MCP server in PolicyLayer and add a rule for reset_constitution: 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 Mcp Vibe Check. Nothing to install.
reset_constitution 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_constitution 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_constitution. 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_constitution is provided by the Mcp Vibe Check MCP server (vinny1575/vibe-check-mcp-server). 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 →