AI agents use vora_update_agent to create or update resources in Vora — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vora environment.
This tool creates or modifies agent configuration and responses (Write category). Severity is medium because a misconfigured voice agent could interact with users in unintended ways, but the impact is limited to the agent's behavior and reversible. The incomplete description and unclear scope of 'improvement' prevent a high confidence rating, though the evidence strongly suggests Write over other categories.
From the tool's definition Tool description states 'Incrementally improve your voice agent' and 'Add new objection responses', indicating modification of agent configuration/behavior.
Attacks that exploit this kind of access
Incrementally improve your voice agent without full recompilation. Use this to: - Add new objection responses based on what you. It is categorised as a Write tool in the Vora MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vora MCP server in PolicyLayer and add a rule for vora_update_agent: 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 Vora. Nothing to install.
vora_update_agent 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 vora_update_agent 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 vora_update_agent. 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.
vora_update_agent is provided by the Vora MCP server (stefanstojanovicstefa-creator/vora-voice-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 →