Drop a vibe at a location — share mood observations, curated POI reviews, event reports, or any location-relevant content. Supports AI image/video generation, custom visual effect prompts, and event-based expiry.
Risk signalsHandles credentials or secrets (apiKey) · High parameter count (14 properties)
Part of the MOD Vibe server.
Free to start. No card required.
AI agents may call drop_vibe to permanently remove or destroy resources in MOD Vibe. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call drop_vibe in a loop, permanently destroying resources in MOD Vibe. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"drop_vibe"
]
}See the full MOD Vibe policy for all 16 tools.
These attack patterns abuse exactly the kind of access drop_vibe gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Drop a vibe at a location — share mood observations, curated POI reviews, event reports, or any location-relevant content. Supports AI image/video generation, custom visual effect prompts, and event-based expiry.. It is categorised as a Destructive tool in the MOD Vibe MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MOD Vibe MCP server in PolicyLayer and add a rule for drop_vibe: 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 MOD Vibe. Nothing to install.
drop_vibe 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 drop_vibe 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 drop_vibe. 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.
drop_vibe is provided by the MOD Vibe MCP server (MOD_Vibes/mod-vibe-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 MOD Vibe tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.