AI agents use agenda_add_goal to create or update resources in VibeServe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VibeServe environment.
This tool creates a new goal record with optional metadata (type, areas, due date, target metric). It modifies state by inserting data into an agenda system, which is a Write operation. The action is reversible (goals can be deleted or modified later), so it does not qualify as Destructive.
From the tool's definition Tool name 'agenda_add_goal' and description 'Add a single goal to the agenda' indicate creation of new data (goal insertion). The phrase 'Add...to the agenda' explicitly describes a write operation that creates a new record reversibly.
Attacks that exploit this kind of access
Add a single goal to the agenda with optional type, areas, due date and target metric. It is categorised as a Write tool in the VibeServe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VibeServe MCP server in PolicyLayer and add a rule for agenda_add_goal: 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 VibeServe. Nothing to install.
agenda_add_goal 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 agenda_add_goal 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 agenda_add_goal. 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.
agenda_add_goal is provided by the VibeServe MCP server (ncsound919/vibeserve). 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 →