AI agents call clear-vectors to permanently remove resources in Ultra MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes all indexed vectors associated with a project, which cannot be undone. While the impact is scoped to vector indexes rather than core application data, the irreversible nature of bulk deletion and the potential to disrupt downstream systems that depend on those vectors (search, retrieval, recommendations) elevates this to Destructive rather than Write.
From the tool's definition Tool name 'clear-vectors' and description 'Clear all indexed vectors for a project' indicate irreversible deletion of indexed data. The verb 'clear' combined with 'all' and the scope of 'for a project' demonstrates bulk deletion without recovery options.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear-vectors gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ultra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear-vectors:
{
"version": "1",
"default": "deny",
"hide": [
"clear-vectors"
]
}clear-vectors disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear all indexed vectors for a project. It is categorised as a Destructive tool in the Ultra MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ultra MCP server in PolicyLayer and add a rule for clear-vectors: 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 Ultra MCP. Nothing to install.
clear-vectors 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 clear-vectors 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 clear-vectors. 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.
clear-vectors is provided by the Ultra MCP server (realmikechong/ultra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Ultra MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 Ultra MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.