Uninstall OakVar modules
AI agents call oakvar_module_uninstall to permanently remove resources in OakVar MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Uninstalling modules removes functionality and data from the system irreversibly. While not as severe as deleting user data, it destroys the system's configuration state and could disable critical annotation pipelines that users depend on. The operation cannot be reversed without explicit reinstallation action.
From the tool's definition Tool name 'oakvar_module_uninstall' and description 'Uninstall OakVar modules' indicate removal of installed modules, which is an irreversible operation that cannot be undone without reinstallation.
Attacks that exploit this kind of access
Uninstall OakVar modules. It is categorised as a Destructive tool in the OakVar MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OakVar MCP Server MCP server in PolicyLayer and add a rule for oakvar_module_uninstall: 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 OakVar MCP Server. Nothing to install.
oakvar_module_uninstall 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 oakvar_module_uninstall 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 oakvar_module_uninstall. 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.
oakvar_module_uninstall is provided by the OakVar MCP Server MCP server (miliyarsh/oakvar-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 →