Update an existing ticket in Ravenna
AI agents use update_ticket to create or update resources in Ravenna MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ravenna MCP Server environment.
This tool modifies existing data (tickets) reversibly—updates can be corrected or reverted by subsequent updates. It does not delete data (not Destructive), execute arbitrary code (not Execute), or involve financial transactions (not Financial).
From the tool's definition Tool name is 'update_ticket' and description states 'Update an existing ticket in Ravenna', indicating modification of existing data in the help desk platform.
Attacks that exploit this kind of access
Update an existing ticket in Ravenna. It is categorised as a Write tool in the Ravenna MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ravenna MCP Server MCP server in PolicyLayer and add a rule for update_ticket: 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 Ravenna MCP Server. Nothing to install.
update_ticket 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 update_ticket 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 update_ticket. 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.
update_ticket is provided by the Ravenna MCP Server MCP server (ravennahq/ravenna-mcp-server). 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 →