vibecontrols_ai_prompts_update
Update an existing AI prompt.
This record as markdown: /tools/vibecontrols-mcp/vibecontrols-ai-prompts-update.md
What vibecontrols_ai_prompts_update does on Vibecontrols
AI agents use vibecontrols_ai_prompts_update to create or update resources in Vibecontrols, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibecontrols environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Prompt ID |
name | string | — | |
tags | array | — | |
status | string | — | |
content | string | — | |
category | string | — | |
isShared | boolean | — | |
metadata | object | — | |
variables | object | — | |
description | string | — |
Parameters from the server's own tool schema.
Why vibecontrols_ai_prompts_update is rated Medium
An AI agent can call vibecontrols_ai_prompts_update faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (content) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs vibecontrols_ai_prompts_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_ai_prompts_update, this is the rule to start with:
vibecontrols_ai_prompts_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_ai_prompts_update call is checked against it from then on.
Questions about vibecontrols_ai_prompts_update
Update an existing AI prompt. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
vibecontrols_ai_prompts_update accepts 10 parameters: id, name, tags, status, content, category, isShared, metadata, variables, description. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_ai_prompts_update: 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 Vibecontrols. Nothing to install.
vibecontrols_ai_prompts_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vibecontrols_ai_prompts_update 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 vibecontrols_ai_prompts_update. 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.
vibecontrols_ai_prompts_update is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vibecontrols, and thousands of servers like it.
This server
Across the catalogue